Separate FBM and FBA
Define which orders ship from your stock to customers and which goods are prepared for FBA replenishment. Keep their inventory and handling steps separate.
Amazon: European fulfilment
Plan FBM orders separately from FBA replenishment. Agree local inventory, labels and returns before launch.
Speak with salesWAYFIRST · PROJECT PLANNING
Priorities for your channel
SKU and shipment plan
For FBM, test SKU mapping and shipment updates. For FBA, reconcile the approved shipment plan, item and carton labels and quantities before preparation.
Returns and removals
Match customer returns separately from FBA removals. Check identity, condition and quantity; restock only under agreed approval rules.
WAYFIRST · HAGEN
From selling channel to warehouse handling
Warehouse location and handling are agreed around your products, dimensions, daily volumes and returns. Before inbound delivery, confirm product acceptance, capacity, packaging samples and the inspection report you need.
View the Hagen warehouse →
WAYFIRST · PROJECT PLANNING
When is your workflow ready to launch?
Adapt these proposed checks with your team. Launch readiness requires a recorded test result and a named owner.
01 · Products and variants
Every test line identifies the correct warehouse item, including variants and sets. Evidence: approved SKU mapping.
02 · Inventory reconciliation
Receiving, reservation and blocked stock produce the agreed sellable balance. Evidence: before-and-after reconciliation.
03 · Order and cancellation
An order is processed once. Test cancellation before picking and replay of a handover. Evidence: test log.
04 · Parcel and tracking
Label, quantity, carrier and tracking match the order; test partial shipments where needed. Evidence: sample label and status update.
05 · Return and approval
Match the return and document condition. Uncertain goods remain blocked; resale and refund need separate approval. Evidence: return report.
06 · Failure and recovery
Missing data or a failed handover produces an alert and a controlled retry. Evidence: failure test with a named owner.
Editable template for test results, evidence and approval.
Download launch checklist (CSV) ↓Agree responsibilities before launch
Record the final allocation of tasks in the agreed service scope.
Seller / store team
Maintain the seller account, product data and customer promises; provide account requirements. Own approvals for goods handling, refunds and customer communication.
Wayfirst · agreed warehouse scope
Plan receiving, storage, picking, packing and return inspection within the agreed scope. Define report fields, exception handling and contacts together.
System partner and carrier
Name a system owner for data handover and status updates. Agree collection, transport service and transit exceptions with the carrier.
WAYFIRST
Clarify before launch
Is a ready-made connection available?
We review your store or ERP, data fields and available handover methods. Connection and scope are confirmed after a documented test.
What timings and costs apply?
Receiving times, order cut-off, return reporting and exception handling are agreed for your volume and products. The quote should separate inbound handling, storage, dispatch, returns and additional work.
What is needed for the review?
Platform and market, product dimensions and weights, SKU and variant counts, daily volumes and peaks, returns profile, system, a sample order and a sample label.
Official reference and scope
Amazon
Amazon · Selling and fulfilment ↗Amazon distinguishes FBA from seller fulfilment. The proposals on this page help define warehouse tasks for each model.
Discuss your platform operations
Share destination markets, product types, SKU count, monthly volume and peaks, return needs and your existing store or ERP system.