One SKU across several channels: decide what stock each order can use

Start with the unit the warehouse can actually pick

Selling the same product on Shopify, eBay and another storefront creates several listing records, but it does not create more physical stock. Start with one warehouse SKU for each distinct product and variant. Record its selling unit, barcode where used, owner and approved dispatch location. Then connect each channel listing and variant ID to that record. A matching product name is insufficient when two pages describe different colours, pack sizes or accessories.

Make the mapping readable by the people handling orders. A useful row contains warehouse SKU, channel, store account, listing ID, variant ID, units per order line and mapping version. If one listing sells a pair and another sells a single item, record the conversion explicitly. When an old listing remains active during a migration, identify whether it draws on the same stock. This prevents two catalogue rows from being treated as two supplies.

Separate stock held from stock a new order can use

Use a shared state dictionary before discussing synchronisation speed. Shopify distinguishes on-hand, available, committed, unavailable and incoming quantities. Its reviewed guidance defines on-hand as the total of committed, unavailable and available stock at a location. Those definitions provide a useful starting point for Shopify records, while the warehouse may also need operational details such as waiting for a quantity check, awaiting packing approval or held for a particular launch.

Write down how the warehouse states map to each receiving system. For example, twelve units may be physically present while two await inspection and three have already been allocated. The remaining seven are candidates for release under your agreed process. This is an illustrative count, not a platform configuration. Record who approves the change from received to releasable, and whether each channel may use that location. Incoming replenishment needs its own expected arrival record.

Choose one owner for each stock decision

Specify which system owns the physical count, which system reserves units for orders and which process publishes channel availability. These responsibilities may sit together, but should still be named. A warehouse adjustment and a marketplace order can arrive close together; without an agreed sequence, each system may overwrite a valid decision made elsewhere. Ask the implementation team to describe the direction of every update, the fields changed and the acknowledgement returned.

Agree how manual holds enter that process. A reservation for wholesale, replacement orders or a launch should have a reference, quantity, reason, authoriser and release condition. Include it in the availability calculation that the relevant connection actually uses. Do not assume a note in a spreadsheet will constrain checkout. Equally, do not alter the physical count to represent a commercial allocation. Preserve both the stock observation and the decision about its next permitted use.

Test the last unit and overlapping orders

Build a small test list around events that compete for the same units. Include two channels attempting to use the last item, a point-of-sale purchase if relevant, a changed order quantity, a cancelled order and a disconnected connection that later retries. For each case, capture the starting warehouse count, displayed channel quantities, order references, event times and final allocation. Decide in advance which result counts as a successful test and who can authorise live use.

A connection that worked once has not yet demonstrated how it handles overlapping updates. Test a manual reservation followed by the next automatic update, and an adjustment followed by a delayed order import. Keep the logs and compare all receiving records. If the test produces a duplicate allocation, pause release of the affected SKU, identify the competing references and reconcile the physical units. Use the agreed fallback process until the implementation team resolves the cause.

Test a campaign reservation without changing the physical count

Use this illustrative sample before a campaign: five approved units are physically present, two are reserved for the launch, and three remain available to ordinary orders. A Shopify order requests two units while a marketplace order requests two. The ordinary pool cannot fulfil both in full. The allocation owner should apply the agreed order sequence and place the unfulfilled requirement on hold, unless the merchant separately authorises release of campaign stock.

Repeat the exercise after a delayed availability update and a cancelled order. Check that the next update still respects the two-unit campaign reservation, and that a cancellation releases only the units actually allocated to that order. Agree the connection scope, fields and decision sequence with the actual implementation team before relying on automatic stock updates.

• Retain the campaign reference, reserved quantity, authoriser and condition for releasing it.
• Record each competing order's import time, allocation result and acknowledgement; retain the original channel reference.
• Give an unresolved shortage or failed update a named owner and a review time, and agree who can pause the affected offer.
• Keep returned goods awaiting inspection outside both pools until the authorised condition decision is recorded.

Connect every allocation to dispatch feedback

For each channel, define the handover from accepted order to picking instruction. Retain the original channel order number, internal fulfilment reference, SKU quantities, approved address version and any hold. If two storefront orders are combined physically, preserve both order references and show what entered the parcel. Combining cartons should not erase the order history or imply that every channel supports the same tracking update method.

Agree who sends the carrier reference back, what event triggers that update and how a failed response is retried. Label creation, warehouse release and carrier acceptance are separate observations. Keep the timestamps that apply to each. If the channel says dispatched while the warehouse is still waiting for an address correction, send the discrepancy to the named owner with the order and parcel references. Correct the source of the mismatch before publishing another unsupported status.

Review cancellations, returns and the daily balance

A cancellation should restore availability only after the allocated units are released through the agreed process. If picking or dispatch has already started, record where the goods actually are and obtain the next instruction. Similarly, a return arriving at US partner warehouse should enter the receiving and condition review before it becomes sellable again. Record its original order, return reference, observed quantity, inspection status and authorised destination within the stock pool.

During a trial, compare opening stock, receipts, allocations, releases, returns and adjustments for the sample SKUs at an agreed review point. Investigate differences using event records instead of forcing all screens to the same number. Bring the SKU map, example orders and ownership decisions when discussing a custom API or Shopify connection with Jeton Express. The useful outcome is a tested allocation process and a clear exception contact for every channel you intend to use.

Keep incoming replenishment outside the available channel balance

Retain the inbound batch reference, expected SKU quantities, receiving location and current milestone separately from the units available to new orders. A shipment departure or arrival notice provides a transport record; warehouse receipt, any agreed hold and release into channel stock need their own events. Confirm how the actual connected systems apply those events.

After release, record the quantity made available and the channel allocation decision. Investigate shortages against the batch list and update the replenishment review for affected variants. When estimating future cover from an available balance, avoid deducting commitments already excluded by its definition. Use the same location, counting unit and snapshot time for the comparison.