🏪SellerTroubleshooting & ErrorsRecentUpdated Jul 12, 2026·Verified against the app Jul 12, 2026

FBF Shipment, Label & Scanning Errors

#errors#fbf#labels#barcodes#boxes#scanning
Troubleshooting · FBF, Labels & Scanning

Everything that can block an FBF inbound shipment: the box-allocation rules in step 2, the confirmation gates in step 4, label-PDF download errors, the UNPRINTED receiving block, and what you can still cancel. Each card quotes the exact message.

How to read this page

Errors here come from three places: the shipment wizard (inline Arabic messages), the label-PDF endpoints (English messages with lowercase codes like wrong_mode), and the warehouse receiving process (platform-side). Match your message to a card; if you only have a code, use the error code index.

Box allocation errors (step 2)

Step 2 (Boxes & Dimensions) enforces one rule: every declared unit is in exactly one box, and every box count adds up. These are the exact messages:

CodeExact messageMeaning
NO_BOXES«يجب إضافة صندوق واحد على الأقل»The shipment has no boxes at all.
EMPTY_BOX«الصندوق لا يحتوي على أي منتج»A box exists but nothing is allocated into it.
UNDER_ALLOCATED«لم يتم توزيع {n} قطعة من منتج بعد»Some declared units of a product are not in any box yet.
OVER_ALLOCATED«تم تخصيص {n} قطعة من منتج ولكن الكمية المختارة {m} فقط»Boxes contain more units of a product than the shipment declares.
COUNT_MISMATCH«إجمالي قطع الصندوق ({sum}) لا يساوي العدد المسجّل ({count})»The box’s declared item count does not equal the sum of its lines.
NON_INTEGER«الكمية يجب أن تكون عدداً صحيحاً (بدون كسور)»A quantity was entered with decimals.
ZERO_QUANTITY«أزل المنتج أو حدّد كمية أكبر من صفر»A product line in a box has quantity 0 — remove it or give it a quantity.
UNDER_ALLOCATEDUnits not fully distributed into boxes
What you see

«لم يتم توزيع 5 قطعة من منتج بعد» (“5 units of a product are not distributed yet”) and the continue button stays blocked.

Likely causes
  • You declared, say, 20 units of a product but the boxes only contain 15.
  • You added a box but forgot to allocate the last product into it.
How to fix it
  1. Open each box and check its product lines against the shipment’s product list.
  2. Add the missing units to an existing box or create a new box for them.
  3. Confirm each box’s total count matches its contents — then continue.
When to contact support

Not a support case — this is always resolvable in the wizard.

🚫Common Mistake

Do not “fix” a mismatch by editing the box’s declared item count to whatever silences the message — the warehouse counts physical units at receiving, and mismatches there become discrepancy cases.

Confirmation blocks (step 4)

Unit-label mode not chosen
What you see

“Please choose the unit-label printing responsibility before confirming.” («يرجى اختيار مسؤولية طباعة ملصقات الوحدات قبل التأكيد.»)

Likely causes
  • Unit-barcode labelling is enabled and the shipment needs a decision: who prints the per-unit FWU labels — you or Fawran.
How to fix it
  1. In step 4, pick either Seller prints unit labels (FWU) or Fawran prints unit labels during receiving.
  2. You can change this later from the Barcode Center, but only until the shipment is received.
Carton attestation not confirmed
What you see

“You must confirm printing and attaching the carton labels before sending the shipment.” («يجب تأكيد طباعة وإلصاق ملصقات الكراتين قبل إرسال الشحنة.»)

Likely causes
  • The mandatory checkbox «أتعهّد بطباعة وإلصاق جميع ملصقات الكراتين على كل صندوق قبل تسليم الشحنة.» (“I undertake to print and attach all carton labels on every box before handing off the shipment.”) is unticked. Carton labels are ALWAYS the seller’s responsibility, in every mode.
How to fix it
  1. Actually print the carton labels and attach one to each box.
  2. Tick the attestation checkbox, then confirm the shipment.
Unit attestation not confirmed (SELLER_PRINTS only)
What you see

“You must confirm attaching the unit labels before sending the shipment.” («يجب تأكيد إلصاق ملصقات الوحدات قبل إرسال الشحنة.»)

Likely causes
  • You chose seller-printed unit labels, so a second checkbox appears: «أتعهّد بطباعة وإلصاق جميع ملصقات الوحدات (FWU) على كل وحدة قبل تسليم الشحنة.» — it is unticked.
How to fix it
  1. Print the FWU unit labels (the PDF becomes available after creation and in the Barcode Center) and attach one per unit.
  2. Tick the unit attestation, then confirm.
When to contact support

If you cannot print unit labels, switch the shipment to Fawran-prints mode instead of attesting falsely — unattested units block receiving.

Warehouse availability block

No platform warehouses ready for pickup
What you see

“No platform warehouses ready for pickup” («لا توجد مستودعات منصة جاهزة للاستلام») with the explanation «مستودعات المنصة لم تُربط بعد بشركة لوجستية. لا يمكن إنشاء شحنة FBF حتى يكمل فريقنا هذا الإعداد.» (“Platform warehouses are not linked to a logistics company yet. An FBF shipment cannot be created until our team completes this setup.”)

Likely causes
  • A platform-side setup gap — destination warehouses exist but are not operationally ready. Nothing on your side causes this.
How to fix it
  1. Wait and retry later — this resolves when the platform completes the linkage.
  2. Your draft is auto-saved; you lose nothing by coming back.
When to contact support

If it persists more than a working day, open a support ticket (Shipping & fulfillment → FBF inbound) so the team is aware.

Unit-label PDF errors

Downloading unit labels can return one of three exact errors:

feature_disabledUnit-barcode printing is not activated yet
What you see

“Unit-barcode printing is pending Admin activation (SELLER_UNIT_BARCODE_MODE=off).” when downloading unit labels.

Likely causes
  • The unit-barcode service is still awaiting platform activation — the Barcode Center shows matching “pending activation” banners today.
How to fix it
  1. Nothing to fix on your side; carton labels, the shipment barcode and the manifest still download normally.
  2. Ship with carton labels as usual — Fawran handles unit labelling during receiving while the feature is dark.
When to contact support

No ticket needed; activation is a platform rollout, not a fault.

wrong_modeThis shipment is in Fawran-prints mode
What you see

“Unit labels are printed by Fawran during receiving for this shipment.” when trying to download unit labels.

Likely causes
  • The shipment’s unit-label mode is FAWRAN_PRINTS — there are no seller-printable unit labels for it, by design.
How to fix it
  1. Do not print or attach any unit labels for this shipment — Fawran prints and attaches them at the warehouse.
  2. If you intended to print them yourself, change the mode to SELLER_PRINTS from the Barcode Center — possible only before the shipment is received.
no_allocationNo unit barcodes allocated yet
What you see

“No unit barcodes have been allocated for this shipment yet.”

Likely causes
  • The shipment is in SELLER_PRINTS mode but the per-unit barcode allocation has not happened or did not complete.
How to fix it
  1. Open the Barcode Center row for this shipment and use its allocate action, then retry the download.
  2. If allocation still produces nothing, retry once after a few minutes.
When to contact support

If allocation keeps failing, open a support ticket (Shipping & fulfillment) with the shipment number.

UNPRINTED and receiving blocks

UNPRINTEDUnits rejected at warehouse scan as UNPRINTED
What you see

You do not see this in your own app — the warehouse reports that receiving is blocked because units scan as UNPRINTED (a unit barcode exists in the system but no printed label is attached and scanned yet).

Likely causes
  • Under FAWRAN_PRINTS: normal and expected — units start UNPRINTED and the warehouse prints, attaches and scans the labels during receiving. The app tells you: “Do not attach unit barcodes yourself — receiving is blocked until the warehouse prints, attaches and scans them (carton labels remain your responsibility at all times).”
  • Under SELLER_PRINTS: you attested but some units arrived without their printed FWU labels attached.
How to fix it
  1. FAWRAN_PRINTS: nothing to do — the warehouse resolves it as part of receiving.
  2. SELLER_PRINTS: the warehouse cannot accept unlabelled units; coordinate through support to either have the units labelled per the warehouse process or returned for labelling.
  3. Never photocopy or hand-write barcode labels.
When to contact support

For SELLER_PRINTS blocks, open a support ticket (Shipping & fulfillment → FBF inbound) with the shipment number and which SKUs are affected.

Cancelling an FBF shipment

Cancel is missing on an FBF shipment
What you see

The cancel action (with confirmation «هل أنت متأكد من إلغاء هذه الشحنة؟» — “Are you sure you want to cancel this shipment?”) is not offered.

Likely causes
  • Cancellation is only possible while the shipment is DRAFT or PENDING_PICKUP. Once a captain is assigned or the shipment is in transit/received, it cannot be cancelled from your side.
  • There is also no editing after submission — submitted content is fixed.
How to fix it
  1. Check the shipment status chip: only DRAFT / PENDING_PICKUP can be cancelled.
  2. If it is already moving, wait for receiving and manage the stock afterwards (e.g. restock retrieval).
When to contact support

If pickup has clearly not happened for days yet the status left PENDING_PICKUP, open a support ticket with the shipment number.

Before you contact support

  • Note the shipment number and its current status.
  • Copy the exact error (code and message) and where it appeared (wizard step, Barcode Center, download).
  • List affected SKUs and quantities.
  • Attach screenshots; for label problems, attach a photo of the printed label if relevant.

Was this article helpful?