Popup market inventory: the event-ops layer around your market stall

Setting up a market-stall location in Shopify is the easy half of event selling — an afternoon of admin. The other half is everything that happens around the event, and that's where money quietly leaks: vans over-loaded with stock that never sells, cash drawers nobody reconciled until Monday, and an event sales spike that poisons your reorder math for a quarter. This piece covers that event-ops layer — the load-out forecast, what to bring, daily reconciliation, the overnight call, and the leftovers. For the Shopify architecture itself, the market-stall location, taking stock out, and transferring it back, the market-stall POS location guide owns that routine completely; this article builds on it rather than repeating it.

The load-out forecast: footfall × attach rate, not optimism

The default load-out method is "pack until the van looks full." The working method is one multiplication:

Expected visitors × attach rate = expected units sold

Worked example, with illustrative numbers. You sell dog harnesses and leashes, and you've booked a two-day market where the organizer expects roughly 400 visitors a day — 800 across the weekend. From your last event (or, for a first event, a conservative planning guess of 5–8%), your attach rate — the share of visitors who buy a harness — is 8%:

800 × 0.08 = 64 harnesses

Sixty-four units, not 200. Now split that across the size curve your online data shows — say S 25% / M 45% / L 30%:

• S: 64 × 0.25 = 16
• M: 64 × 0.45 = 29
• L: 64 × 0.30 = 19

One adjustment before you load: your hero size sells out first at events (M, here), and a sold-out table stops selling the whole line. Load 1.5× on the hero — 29 × 1.5 ≈ 43 — bringing the load to 16 + 43 + 19 = 78 units. The extra 14 are insurance on the size that carries the weekend, and the honest way to carry them is from van stock rather than the formal transfer, so the transfer still reflects the 64 you planned to sell through.

The attach rate is the only soft number in the whole calculation, and it hardens fast: after your first event, attach rate = units sold ÷ estimated visitors, and every forecast after that runs on history instead of hope.

What to bring beyond stock

The stock list is one of four checklists. The other three:

• Payment redundancy. A backup card reader and a charged power bank. One reader on one battery is a single point of failure for the day's revenue; a spare reader costs a fraction of one lost Saturday of card sales.
• Packaging. Events consume bags, tissue, and stickers at a rate online ordering never shows — impulse buys want to be carried. Event packaging deserves its own count rather than raiding the mailer shelf; packaging as managed inventory covers the stock discipline behind it.
• Signage with a QR code to your full catalog. You can't load the whole catalog into a stall — that's the point of a curated table. The QR catches the demand you deliberately didn't bring: sizes left home, colors that don't fit the table, the leash that pairs with the harness. The event sells the brand; the catalog closes the rest.
• A printed stock list that matches the transfer. The transfer in Shopify says what left the building; the paper list is what you count against at load-out and again at pack-up. Memory does not survive to Sunday 4 p.m.

Cash discipline: reconcile daily, not after the weekend

A market stall runs three ledgers at once: the cash drawer, card sales, and the stock transfer. The drawer is the one merchants skip, and it's where event shrinkage lives — a dip for parking, a "free one" for a friend, a bill miscounted at dusk. Event shrinkage is real enough to have patterns; inventory shrinkage prevention covers the store-level version, and the event version is the same discipline compressed into ten minutes a night:

1. Count the drawer against the POS cash record; write any over/short on the stock-list sheet.
2. Reconcile card — POS total vs the reader's settlement.
3. Count stock on hand against the paper list; log any gap as unexplained until reconciled, not as "probably sold."
4. Document any van restock on the same sheet, so day two starts from a known quantity.

Step 3 is the one that pays. A size mix that doesn't reconcile on Saturday night is a solvable puzzle; the same gap discovered Monday, from a van parked in a different city, is a shrug — and shrugs compound into shrinkage you never priced.

The overnight call: restock from the van or return to base

Multi-day events add one decision per night: how to cover day two. Check the hero size first — it's the one that will be gone by noon.

• Van has the deficit → restock from the van. Document it on the sheet (and in the transfer notes if you keep the transfer open across days). Ten units of M moved from a box in the van takes two minutes.
• Van doesn't have it → decide honestly. A return-to-base trip for one size is rarely worth the fuel and the missing-table hours. Accept the sell-down, push the sizes you have, and let the QR signage catch what you can't.

The only wrong answer is the undocumented one. A van pull nobody wrote down becomes a phantom discrepancy at reconciliation — and worse, a fake shrinkage signal that sends you hunting for theft that never happened.

After the event: what the numbers can and can't tell you

Back home, the transfer-back reconciliation puts unsold units into sellable stock again — the POS location guide's routine covers it. Then comes the tempting mistake: reading the event's sell-through as demand.

Event buyers behave differently from online buyers. They're walking past a table, buying on touch and conversation, often gifting. A harness that moves at three times its online daily rate across one weekend is describing the event, not the product's normal velocity. Fold that weekend into your reorder math unexamined and you'll over-order for months.

So: report event sell-through separately, and never feed an event spike into base velocity without a caveat — averages that mix a market weekend with ordinary weeks will lie to you about both. Why averaging velocity misleads reordering covers the deeper version of this trap, including the opposite one: a bestseller that wasn't on the table records zero event demand, exactly like a quiet week online, and a naive average under-orders it afterward.

A note on tooling, since it's the one place we'll mention what we build: a single-location ledger like InventoryX's sees each SKU's net stock effect after the fact, so each SKU's net event effect is visible after the fact. What it can't do is make the event-day calls — restock from the van, price a scuffed display unit. Those stay manual. We'd rather say that than imply the app runs your market stall.

Leftovers: the transfer back and the next event

Unsold units have two honest destinations:

• Back into the main location via the transfer, inspected as they're counted.
• Tagged and binned for the next event — a dedicated event bin in your storage, so the next load-out starts from a count instead of a search.

If you do events seasonally — holiday markets, summer fairs — treat event stock as a rotation of its own, with its own bin and its own count; seasonal storage rotation covers the pattern. One rule holds either way: display units and scuffed stock don't slide silently back into sellable inventory. Count them, note them, decide them.

Common questions

How much stock should I bring to a pop-up market? Multiply expected visitors by attach rate: 800 visitors × an 8% attach rate is 64 units, split across your size curve, with roughly 1.5× on the hero size. First event with no history? Plan on 5–8%, treat it as an illustrative guess, and let the first reconciliation give you the real number.

How do I track market sales in Shopify? Through a dedicated market-stall location and POS: transfer stock out before the event, sell against it, transfer the remainder back after. The location setup and reconciliation mechanics live in the market-stall POS guide; your job at the event is the nightly count against the paper stock list.

Should event sales count toward reorder velocity? Generally no, or only with a caveat. Event buyers purchase on impulse and touch at rates online never repeats. Report sell-through separately; folding a market weekend into weekly averages corrupts reorder math in both directions — spike weeks over-order, and unshown bestsellers under-order.

How do I prevent shrinkage at events? Reconcile daily: count the drawer against the POS cash record, match card totals to the reader settlement, and count stock against the transfer list every night. Document van restocks on the spot. Gaps found Saturday night get solved; gaps found Monday become unexplained losses.

What do I do with unsold market stock? Two destinations: transfer it back into your main location, or tag it into a dedicated event bin for the next market. Inspect as you count, keep display and scuffed units out of sellable stock, and if events are seasonal, run the event bin as a proper seasonal rotation.

Next step

Build the load-out sheet for your next event before you pack a single box: visitors × attach rate, the size-curve split, the 1.5× hero adjustment. Ten minutes of arithmetic replaces the pack-until-full default and tells you, afterward, whether the forecast or the footfall was wrong. If the market-stall location itself isn't set up yet — or the transfer-back routine keeps going sideways — start with the market-stall POS location guide and bring this checklist once the plumbing works. Event-driven buying gets even sharper for perishable stock — florist inventory management covers the two-stock model.