🏪SellerOrders & FulfillmentPopularRecentUpdated Jul 12, 2026·Verified against the app Jul 12, 2026

Order Lifecycle Overview

#orders#lifecycle#status#fulfillment#needs action
Orders · Foundations

Your Orders page is a work queue. Each row is one product item to fulfill, and what you can do with it depends entirely on its fulfillment model.

Item-first, not order-first

A customer’s basket can contain items from different sellers and models. Fawran splits it so each row you see is one order item you’re responsible for — you action items, not whole baskets.

Important

Because of this split, several rows can share the same order number — one buyer order that contains three of your products appears as three rows, and each can move (and ship) independently. They are not duplicates. Open any row’s detail page to see all sibling items of that order and switch between them.

Finding your way around

Two sets of tabs organise the queue, and a “Needs action” strip above them tells you where to start:

Tab groupTabs
FulfillmentAll · Market · FBF · FBS
StatusNew Orders · Ready for Dispatch · In Delivery · Delivered · Order History
UI guide
Orders
Orders
Needs action: Awaiting approval (3) · Prepare & mark ready (2) · Ready — awaiting captain (1) · FBS — ship / deliver (1)
AllMarketFBFFBS
New OrdersReady for DispatchIn DeliveryDeliveredOrder History
SearchSearch by order number or product name...
Row: #ORD-284551 · Colombian Coffee Beans 250g · ×2 · Market · COD · Awaiting readiness
Approve
Structural diagram of the real page — not a screenshot.
The orders queue: fulfillment tabs × status tabs, with the Needs-action strip on top

The status tabs group rows by their shipment status: “In Delivery” collects everything dispatched, in transit or out for delivery, and “Order History” collects delivered, cancelled and returned rows (with a cancellation-reason column). Switching the fulfillment tab resets the status tab to New Orders. Search matches the order number or the product name. When every bucket is empty the strip shows the all-clear line: “You're all caught up — no orders need action.”

The status flow

NewA customer placed the order
ProcessingYou approved & are preparing it
Ready for pickup / dispatchMARKET: ready for the captain
Out for delivery
Delivered

Every row actually carries two status tracks — the item’s work status and the shipment’s logistics status. The full meaning of each value is in the Order Status Dictionary.

What you can do, per model

ModelYour actions
MARKETApprove → Ready for Dispatch. A Fawran captain then collects, and Fawran delivers. Cancel is available until the captain side takes over.
FBSApprove → Out for Delivery (a tracking number is required) → Delivered. You drive the whole chain.
FBFNone — “This order is managed by the platform (FBF). You cannot change its status directly.”
Important

For FBF orders you’re hands-off: Fawran picks, packs, ships and delivers from its warehouse. Your job for FBF happened earlier — getting stock into the warehouse.

ℹ️Note

You can cancel a MARKET or FBS item early in its lifecycle, choosing a reason (Seller Request or Customer Request). The exact windows are verified in Cancelling an Order; cancellations count against your performance — see Performance Metrics.

Customer details and payment method

What you see about the buyer depends on who delivers. For MARKET and FBS orders the detail page shows a Delivery Address card — recipient name, address, city/area, delivery notes, a tap-to-call phone number and an open-in-maps link — because you (or the captain collecting from you) need it. For FBF orders no buyer address is shown: Fawran’s warehouse handles delivery.

Each row also carries a payment chip: COD (cash on delivery) or Paid (card). This is display-only context — it changes nothing about how you process the item. The financial details of this step are covered in a dedicated Finance guide coming soon.

Was this article helpful?