Ecommerce operations guide
A multichannel inventory plan defines which stock each channel can sell, which system controls the quantity and how orders reserve it. Merchant-fulfilled Shopify, Amazon and Walmart orders can use an agreed warehouse stock pool when the configuration supports it. Keep inventory transferred to Amazon FBA separate. FHU publishes connection guides for those platforms; each brand still needs tested mappings, allocation and exception rules.
Decision support
Use the same definitions and evidence across every option. A comparison is not reliable when one path uses best-case assumptions and another uses observed operating data.
| Requirement | Brand responsibility | Fulfillment handoff | Acceptance evidence |
|---|---|---|---|
| Source of truth | Name the system that owns each inventory field. | Map SKU and location identifiers. | Field ownership and tested mappings. |
| Availability | Define reservations, safety stock and channel allocation. | Confirm which stock states feed each channel. | Availability tests before and after an order. |
| Exceptions | Assign cancellations, sync failures and overselling alerts. | Agree acknowledgement, retry and escalation rules. | Traceable failed transaction and recovery test. |
| FBA replenishment | Maintain a separate FBA forecast and transfer plan. | Confirm preparation and shipment scope. | Separate warehouse, in-transit and FBA balances. |
Execution
Move to the next step only when the evidence and owner for the current step are clear.
List storefronts, marketplaces, wholesale flows and returns. FHU publishes connection guides for Shopify, Amazon, Walmart and other platforms; a listed connection is a starting point, not proof that every workflow is enabled.
Identify which system owns the catalog, available quantities, orders and shipment status. Preserve consistent SKU identifiers and clarify whether bundles consume components or preassembled stock.
Place concurrent orders, cancel before fulfillment and check stock release. Include an out-of-stock item and an unavailable integration. Reconcile the order IDs and resulting quantities across systems.
When warehouse stock is moved to FBA, record the transfer and track in-transit quantities. Amazon receiving and availability are separate from the 3PL receipt. Merchant-fulfilled stock should not silently include those units.
Define who investigates mismatched balances, aged orders and failed acknowledgements. Returned goods become available only after the agreed inspection and disposition; do not automatically count every return as sellable.
Planning questions
Agree the ownership of quantities and recovery steps before connecting more storefronts.
Merchant-fulfilled orders can share an agreed warehouse stock pool when the connections, SKU mappings and allocation rules support that setup. Confirm the account-specific workflow with FHU. A published connection guide does not establish that every order type or stock state is enabled.
No. Inventory sent into Amazon’s fulfillment network is a separate physical pool. Record warehouse transfers and quantities in transit, then reconcile Amazon receipt and availability. Do not count the same units as available in both places.
Assign one system as the authority for each quantity and location, then map its states into the channels. Distinguish stock on hand from stock reserved for orders, unavailable stock and incoming shipments. Check the resulting balances using representative orders and cancellations.
Define detection, ownership, retry limits and escalation before launch. Test a failed update and its recovery, including duplicate messages and orders that arrive while a connection is unavailable. Agree how the brand will restrict sales when a quantity cannot be trusted.
Boundaries
Primary sources
