Skip to main content

Ecommerce operations guide

One inventory plan. Clear rules for every sales channel.

Multichannel fulfillment works when the systems agree on what can be sold, where it is held and which orders reserve it. A shared warehouse stock pool can support merchant-fulfilled channels when the integration and allocation rules are configured for that workflow. Inventory sent to Amazon FBA is a separate physical pool. Plan its replenishment and reconciliation explicitly rather than treating all channel balances as interchangeable.

Reviewed 2026-10-17 Evidence owner: Fulfillment Hub USA
Conceptual shared inventory connected to multiple storefronts alongside a separate allocated stock group.

Decision support

Decisions to settle before launch

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.

RequirementBrand responsibilityFulfillment handoffAcceptance evidence
Source of truthName the system that owns each inventory field.Map SKU and location identifiers.Field ownership and tested mappings.
AvailabilityDefine reservations, safety stock and channel allocation.Confirm which stock states feed each channel.Availability tests before and after an order.
ExceptionsAssign cancellations, sync failures and overselling alerts.Agree acknowledgement, retry and escalation rules.Traceable failed transaction and recovery test.
FBA replenishmentMaintain a separate FBA forecast and transfer plan.Confirm preparation and shipment scope.Separate warehouse, in-transit and FBA balances.

Execution

From requirements to a working launch

Move to the next step only when the evidence and owner for the current step are clear.

  1. 01

    Map the actual channel mix

    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.

  2. 02

    Choose field-level ownership

    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.

  3. 03

    Test reservations and cancellations

    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.

  4. 04

    Keep FBA transfers separate

    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.

  5. 05

    Reconcile exceptions and returns

    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.

Boundaries

Limitations and review triggers

  • Supported channels, sync timing, order changes and routing behavior depend on the agreed integration configuration.
  • Safety stock and allocation settings reduce exposure but do not promise zero overselling or uninterrupted platform availability.
  • FBA preparation and replenishment are separate from merchant fulfillment; confirm fees, rules and ownership for each flow.