The spreadsheet is still the most underrated piece of infrastructure in cross-border e-commerce
Every serious cross-border operator I know runs on a spreadsheet they’re slightly embarrassed about. The Helium 10 export that gets VLOOKUP’d against a freight forwarder’s rate card. The TikTok Shop settlement file that someone re-saves as CSV every Friday. The Temu price-watch sheet that a VA in Manila updates by hand because the API doesn’t exist. We talk endlessly about Shopify apps, Klaviyo flows, and Amazon PPC automation, but the actual last mile of most operational decisions still terminates in a .xlsx file that someone opens, edits, and emails back. That’s why a small, opinionated launch like SimpleSpread — a native Mac spreadsheet built by Matt Sergeant — is worth more of your attention than the usual AI-wrapper noise on Product Hunt. It’s not an e-commerce tool. But the problem it solves is the exact problem your ops stack has.
What SimpleSpread actually solves, and why the framing matters
Sergeant’s own launch post states the brief with unusual clarity: he wanted a spreadsheet on his Mac that “opens fast, edits an .xlsx file and saves it back, and does nothing else.” He explicitly rejects the three defaults most of us live inside. Numbers converts everything into its own format. Excel is a subscription and a heavy install just to open a CSV. Google Sheets wants a browser and an account.
That last clause is the one cross-border sellers should sit with. Google Sheets requires an account, and accounts are the friction point in every outsourced ops workflow. If you’re running a VA team across time zones, or a 3PL partner you don’t fully trust with your Google Workspace, or a customs broker who just needs one file, “open it in Sheets” is a permissioning decision, not a convenience. A local app that edits the file in place sidesteps the entire identity layer.
The technical claims are also more relevant than they sound. SimpleSpread is a native Mac app written entirely in Swift, with the spreadsheet stack built from scratch — the model, the formula engine, the XLSX reader and writer down to the ZIP layer, plus CSV and the grid. The only outside library is Sparkle for updates. Round-trip fidelity is the headline: styles, number formats, formulas with cached values, merged ranges, and frozen panes all survive when you open a file from Excel, Numbers, or Google Sheets, edit it, and send it back.
For anyone who has ever watched a supplier’s quote sheet lose its number formatting the moment it touched Google Sheets, that sentence is the whole product.
The CSV details that matter to sellers more than to developers
Buried in the feature list is the line that a commenter, Gal Dayan, correctly flagged as the thing “most hobby spreadsheet projects never even think about”: CSV formula injection. A field like =cmd imports as text, never as a formula. SimpleSpread also does delimiter sniffing, BOM and CP1252 detection, and preserves leading zeros.
If you’ve never thought about why that matters, here’s the cross-border version. Your supplier in Shenzhen sends you a CSV of SKUs. One SKU starts with =. Your spreadsheet evaluates it as a formula. Best case it errors. Worst case it executes something. Then you re-export and forward that file to your 3PL, your accountant, or your Amazon case log. You’ve just propagated a payload through your own supply chain. This is not a theoretical risk — it’s a known attack class that gets rediscovered every few years because most tools handle it wrong. A spreadsheet that handles it correctly by default is doing quiet security work your current stack probably isn’t.
The other CSV behaviors — BOM and CP1252 detection, leading-zero preservation — are the exact reasons Chinese and European supplier files break in your pipeline. SKUs like 0071234 becoming 71234 is a class of bug that has cost real sellers real money in mis-shipped inventory. It’s unglamorous. It’s also the difference between a tool you tolerate and a tool you trust.
How it differs from the incumbents — and where the comparison actually lands
Let’s be honest about the competitive set. SimpleSpread is not competing with Excel on features. It’s competing with Excel, Numbers, and Google Sheets on latency and friction, and it’s competing with a long tail of web-based CSV viewers on privacy and round-trip fidelity.
Against Google Sheets, the trade is obvious: you give up collaboration and cloud sync, you get a local file that opens instantly and doesn’t require an account. For a lot of cross-border ops work — supplier negotiations, freight quotes, one-off settlement reconciliations — that trade is correct. You don’t want the file in a shared drive. You want it on your machine, edited, and sent back.
Against Numbers, the argument is format fidelity. Numbers is a fine consumer app that treats .xlsx as a foreign language it grudgingly speaks. SimpleSpread treats .xlsx as the native tongue. For anyone whose counterparties live in Excel, that’s the whole game.
Against Excel, it’s the subscription and the install weight. Sergeant’s point that Excel is “a subscription and a big install for opening a CSV” is a fair characterization of the mismatch. Most people who open CSVs for a living don’t need 90% of Excel. They need a fast grid that doesn’t mangle the file.
The feature set is deliberately narrow: 156 functions with the coercion rules Sheets and Excel share, including SUMIFS with wildcards, XLOOKUP, INDEX/MATCH, IRR/XIRR, dates and text, plus incremental recalc and cycle detection. Editing behavior mirrors Excel — Enter/Edit modes, type-to-replace, F2, ⌘-arrow jumps, fill handle, ⌘D / ⌘R, real undo, Find, zoom. It’s notarized and updates itself in place.
Sergeant is also unusually upfront about what it isn’t: no charts, no conditional formatting, no array formulas, no INDIRECT/OFFSET yet, no collaboration. Frozen panes and merged cells are preserved in the file but not yet drawn. Apple Silicon only, macOS 14 or later, en-US number and date input for now. It’s free, MIT licensed, and on GitHub.
Why Amazon sellers should care more than Shopify ones
Shopify operators tend to live inside apps. The data you care about — orders, inventory, customer LTV — flows through Shopify admin and a stack of Klaviyo and Recharge integrations. You rarely touch a raw file.
Amazon sellers are the opposite. Amazon Seller Central is a reporting engine that outputs spreadsheets, and most serious FBA brands run their P&L, their reimbursement reconciliation, and their inventory forecasting in .xlsx files that get passed between the brand owner, a bookkeeper, and sometimes an agency. The same is true for TikTok Shop settlement reports and Temu seller exports, both of which are still file-first workflows. If your week involves opening three Amazon reports and reconciling them against a freight invoice, you are the target user for a fast local spreadsheet, whether or not you’ve ever heard of SimpleSpread.
Where the math breaks
Two honest caveats. First, the platform lock: Apple Silicon only, macOS 14+, en-US number and date input. If your ops team runs Windows, or your finance lead is on an Intel Mac, or your VA is on a Chromebook, this tool doesn’t exist for them. That’s a real constraint, not a nitpick.
Second, the missing pieces Sergeant himself lists — no charts, no conditional formatting, no array formulas, no INDIRECT/OFFSET — will disqualify it for anyone doing serious modeling. If your inventory forecast relies on OFFSET-driven rolling windows, you’re not the user. The tool is honest about this, which is more than most launches manage.
What cross-border sellers can borrow from this launch
The product itself is a Mac utility. The strategy is a masterclass in how to think about your own ops stack, and there are three things worth stealing.
One: name the incumbent friction explicitly. Sergeant doesn’t say “SimpleSpread is a better spreadsheet.” He says Numbers converts your format, Excel is a subscription, Sheets needs an account. Every one of those is a concrete, verifiable complaint. When you evaluate a new tool for your e-commerce stack — a 3PL, a repricing tool, a returns processor — do the same exercise. Write down the specific friction the incumbent imposes. If you can’t name it in one sentence, you don’t have a reason to switch.
Two: the round-trip test is the only test that matters. “Styles, number formats, formulas with cached values, merged ranges and frozen panes all survive the round trip” is the single most important claim in the launch. It’s also the test most sellers never run. Before you adopt any tool that touches your data, send a real file through it and back. Your supplier’s quote sheet. Your Amazon settlement report. If formatting, formulas, or leading zeros break, the tool is a liability no matter how nice the UI is.
Three: security defaults are a feature. The formula-injection handling is the kind of thing you only appreciate after you’ve been bitten. When you’re evaluating tools that ingest supplier or marketplace files, ask what happens to a cell that starts with =, +, -, or @. If the vendor can’t answer, that’s your answer.
The pivot table turnaround is the real story
The most interesting thing in the whole thread isn’t the feature list. It’s the exchange with Jaewon Seo, who said “no pivot tables would stop me honestly.” Sergeant replied that he’d try, warned he might reject it if it bloated the codebase, and then — per his own follow-up — shipped version 1.3.0 with pivot table support within hours. When Dayan asked whether they were half-built already, Sergeant explained that pivot tables are “just basically SQL’s GROUP BY,” that his SQL background made it straightforward, and that the harder part was replacing the recursive formula engine because it was blowing the stack. He also noted it was Sunday and raining.
Two lessons for operators. First, the speed came from domain expertise, not from magic — a 30-year engineer recognizing a familiar pattern. Second, the constraint that almost killed the feature was architectural, not conceptual. The formula engine had to be rewritten non-recursively before pivots could ship. That’s the same pattern you see in e-commerce ops: the feature you want is easy, the underlying data model is the hard part. If your inventory system can’t support the reporting you want, the reporting tool isn’t the problem.
What I’d watch / test next
If you’re a cross-border operator, here’s what I’d actually do this week. First, download SimpleSpread and run it against your three messiest real files — a supplier quote sheet, an Amazon settlement export, and a TikTok Shop or Temu payout CSV. Check specifically for leading-zero preservation, formula-injection handling, and whether merged cells and frozen panes survive. That’s a 20-minute test that tells you more than any feature list. Second, watch the GitHub repo for whether Find & Replace and Paste Values ship, since Sergeant named both as next. Third, watch whether Windows and Intel Mac support arrive — until then, this is a tool for solo operators and Mac-based finance leads, not for teams. Fourth, and most importantly, use the launch as a template: audit your own stack for the tool you’re tolerating out of habit, and ask whether a narrow, fast, honest alternative would beat it. The spreadsheet didn’t need to be reinvented. It needed to be respected.
