Guide · Operations

From wine inventory spreadsheet to operations hub

Most importers start in Excel. Here is what breaks first, what actually needs to move, and how to migrate without losing the month.

Why the wine inventory spreadsheet stops scaling

A single wine inventory spreadsheet can carry a young importer surprisingly far — SKUs on one tab, a rolling stock count on another, a landed-cost calculator someone built in 2019, and a follow-up list pasted from email. It works until it doesn't. The failure modes are always the same:

  • Data silos. Product master lives in one file, warehouse counts in another, accounts in a third. Nothing reconciles.
  • Landed cost drift. Freight, duty, and FX get updated inconsistently across shipments. Margin numbers quietly stop being true.
  • Reorder decisions by feel. Weeks-of-cover math depends on which tab you trust today. Slow movers get reordered; fast movers stock out.
  • No audit trail. Cells get overwritten. You cannot tell who changed a landed cost, when, or why.

What an operations hub actually replaces

An operations hub like ImportOps Hub is not an accounting replacement — QuickBooks or Xero still keeps the books. The hub owns the operational layer that spreadsheets were standing in for:

Product master

One canonical SKU record: producer, vintage, size, pack, TTB label reference. No more three-tab reconciliation.

Landed cost

Freight, duty, insurance, and FX apply per shipment. Every SKU carries a real cost basis you can trust.

Reorder planning

Weeks-of-cover and depletion velocity are computed from the same inventory snapshot, not eyeballed from a pivot.

Account follow-up

Notes and next actions live on the account, so the person covering the territory next month sees the same history you do.

A migration path that does not blow up the month

  1. 1

    Freeze the source of truth for products.

    Export the current product tab. Clean SKU codes, vintages, and pack sizes once. Import the cleaned list — this becomes the master. Every downstream calculation depends on it.

  2. 2

    Import a single inventory snapshot.

    Pick a date and post one warehouse count. Do not retroactively backfill months of history — start clean and let subsequent snapshots build the trend.

  3. 3

    Rebuild landed cost per shipment.

    For the last two or three shipments, enter freight, duty, insurance, and FX. Every SKU on those shipments now has a defensible cost basis and the reorder view stops lying.

  4. 4

    Move account notes over as-is.

    Do not try to rewrite history. Paste the last quarter of follow-ups per account so the next call has context. New notes go in the hub from day one.

  5. 5

    Archive the spreadsheet, do not delete.

    Keep it read-only for a month. When nobody has opened it in 30 days, you know the migration stuck.

See how ImportOps Hub handles it

Product master, landed cost, inventory snapshots, and reorder planning in one operations layer — without replacing your accounting system.

Start free