Labels only matter because someone scans them. On Fawran that someone is never you: the captain scans at pickup and the warehouse scans at receiving. Your job ends at printing and attaching correctly — this guide explains what those scans check and what happens when they disagree with reality.
Who scans, and when
- At pickup (By Platform): the captain scans the shipment/boxes to confirm what actually left your warehouse.
- At receiving: the warehouse scans the shipment, cartons and — where applicable — each FWU unit, comparing everything to your declaration.
- You never scan. There is no seller scan step anywhere in the inbound flow.
What a scan can find
Scans exist to catch mismatches between the declared and the physical. From your side, the outcomes look like this:
| Situation | What happens, from your perspective |
|---|---|
| Duplicate scan (same label twice) | The second scan is rejected — no double counting. If it points at two physical pieces wearing the same label, those units are set aside and a case is opened. |
| Wrong unit / not part of this product | The unit is separated at inspection and appears in your cases as "not part of this product" — receiving of the healthy units continues. |
| Unit belongs to another shipment | The scan flags it; the unit is handled apart and receiving of your shipment may be partially delayed while it’s resolved. |
| Wrong warehouse | The shipment/units are flagged at the gate; the platform re-routes internally — expect delay, not data loss. |
Unit not labeled yet (UNPRINTED) | The unit is rejected at the scan until its label is printed and attached (by the warehouse under Fawran-prints; by you before handover under seller-prints). |
These are the seller-visible effects. The warehouse’s internal scan tooling has more detail than this, but everything meaningful to you surfaces as shipment progress, cases in Inventory Cases, or a support conversation.
Permanent identity: invalid and already-bound barcodes
- Invalid format: anything that isn’t a real FWU code is refused outright — the Barcode Center itself validates with «صيغة الباركود غير صالحة (مثال: FWU-2026-000000000001-C7)».
- Already-bound: an FWU barcode belongs to exactly one physical unit, forever. A label moved to a different piece, or a photocopied label, fails identity verification — most visibly on returns, where the warehouse confirms the returning unit is the original.
Never "recycle" labels between pieces and never attach two copies of one label. The permanence of the FWU identity is what protects you: it proves which exact units are yours at every custody handover.
What you can fix vs what needs support
| You can fix it yourself | Warehouse / support territory |
|---|---|
| A damaged or unreadable label before handover — reprint from the Barcode Center (reason required; the same barcode is reused). | Anything discovered after handover — mis-scans, separated units, wrong-shipment flags. Track it in Inventory Cases and reply to case requests. |
| Wrong box contents before submitting — fix the allocation at step 2 of the wizard. | Identity conflicts (duplicate/bound barcodes) — the warehouse arbitrates using the unit’s lifecycle log. |
| Choosing/switching the unit-label mode before receiving. | Re-routing goods that reached the wrong warehouse. |
If a case mentions a specific unit, look it up in the Barcode Center’s Unit Lookup — the lifecycle log usually answers "where did this unit actually go?" faster than a support thread.