Complete Examples

Follow Ahmad end-to-end: email code sign-in, the 3-step store wizard, all six verification steps with sample values, and what to do when Fawran asks for a better document.

Ahmad lists Colombian Coffee Beans 250g by entering its barcode, matching the verified catalog item, and completing the 4-step offer wizard — plus the Arabic-name validation error and how drafts activate.

Ahmad’s French Press 600ml isn’t in the Fawran catalog. He creates a candidate catalog product, sells immediately while admin reviews it — and learns what to do if the candidate is later rejected.

Fawran has no variant matrix — one product is one offer. Ahmad lists a t-shirt in Blue/Black × M/L as four separate products with a clear naming convention, and avoids the variant-matrix trap.

Ahmad enrolls his coffee in FBF through the add-to-inventory wizard — release date, no quantity field, and why the sellable number only appears after warehouse receiving.

The flagship walkthrough: Ahmad ships 20 coffee units in 2 cartons with platform pickup, follows every status to activation, fixes a box-allocation error, and handles one unit damaged at receiving.

The seller-prints variant of the inbound flow: allocate FWU barcodes, download the carton and unit PDFs, attach each label on the right surface, sign both pledges — and what happens if one unit label is missed.

Ahmad cancels order ORD-284551 before approving it: the confirm dialog, the cancellation reason, where the row goes, what happens to reserved stock — and the performance cost of cancelling.

Ahmad tries to cancel a MARKET order after the captain has taken it: no cancel action anywhere. Why eligibility has passed, what his real options are, and how a refused delivery turns into a return.

Ahmad filters Sales Reports to the last 30 days of delivered orders, exports the CSV, and reads each column correctly — including which columns to leave for the coming Finance guide.

Ahmad hires Samia and invites her as Staff from Settings → Team Members: the invite form, the pending invitation, acceptance by email link, role limits — and what to do when an invite expires.

Ahmad’s inbound FBF shipment sits at receiving and support mentions units are UNPRINTED. What that status really means, why he must not attach his own unit labels, and what the seller-prints branch looks like.

Ahmad receives MARKET order ORD-284551, approves it, prepares it, marks it ready — then watches the captain and warehouse carry it to the customer, status by status.

Ahmad’s MARKET order sits at CAPTAIN_ASSIGNMENT_PENDING a day after he marked it ready. What to check, what to keep doing, when to open a ticket — and why cancelling is the wrong reflex.

Ahmad fulfills FBS order ORD-291406 himself: approve, package, dispatch with tracking number TRK-7789-JO and a courier name, then mark delivered — and why dispatch without tracking is blocked.

Ahmad’s courier finds nobody at the address. What the app honestly supports: the item stays OUT_FOR_DELIVERY, retries are between Ahmad and his courier, and a final failure is handled by cancellation plus a support ticket.

A buyer returns Ahmad’s FBF coffee unit. The warehouse validates its permanent FWU identity, grades it A, and the case lands in his Warehouse Returns workspace awaiting his decision — here is what each option really does today.

Ahmad’s returned blender is graded D (unsellable). What his decision options really do today, how he disposes with a reason, and the honest way to dispute a grade — with photos, through a ticket.

A return arrives at the warehouse, but the unit’s permanent FWU barcode belongs to a different order. How identity validation catches it, where the case appears for Ahmad, and the claim/return/dispose outcomes.

Ahmad reports 3 missing units from an inbound FBF shipment: picking the exact category path, writing a description that answers questions before they’re asked, attaching photos and a packing list, and riding the ticket to RESOLVED.