Fawran ships in the open: some seller features are visible but not finished, and a few are switched off until the platform turns them on. This page is the honest map — check it whenever a button seems to do nothing, so you can stop looking and use the path that works today.
Coming soon — not built yet
These appear in the app (usually as a “Coming soon” screen) but have no working feature behind them yet. Don’t plan work around them.
| Area | What you see today | What to do instead |
|---|---|---|
| Store Reviews | A “Coming soon” page. Customer ratings are not shown to sellers yet. | Watch your Return Rate and Cancellation Rate in Sales Reports as your quality signals for now. |
| Packages | A placeholder page (“My Packages”). | Ignore it — nothing to configure. |
| In-app Help Center | The Seller app’s Help Center now links out to this full Help Center. | Use this Help Center (search or browse) — you’re already here. |
| Seller Training | A placeholder page. | Use the guided learning paths and Complete Examples in this Help Center. |
| Knowledge Base | A placeholder page inside the app. | Search this Help Center instead. |
| Smart Assistant | A chat surface that is not switched on yet. | Help buttons open a support ticket; use this Help Center for how-to answers. |
| Disputes tab | The Support area shows a Disputes tab with an empty state — the disputes backend is not connected. | Raise disputes as a support ticket (Returns & Refunds) with your evidence attached. |
For the assistant specifically, see Using the Smart Assistant — today its Help buttons route you to a support ticket.
Awaiting platform activation — flag-gated
These are fully built and visible, but an action is blocked until Fawran activates it for your store. The screen tells you it is pending; it is not a bug.
| Feature | What happens today | What to do instead |
|---|---|---|
| Barcode Center actions (unit labels) | Allocation and unit-label downloads show a “pending Admin activation” state. | Carton labels still work. See Unit-Label Modes for how printing responsibility is decided. |
| MARKET shipment barcode panel | The shipment-barcode / ready-for-pickup panel shows a “will be enabled soon” notice. | Mark the order ready as normal; the platform handles pickup. See MARKET Order Workflow. |
| Warehouse-return decisions (except Dispose) | Transfer to FBF, Return to me and Keep stored return “This action isn’t enabled yet — coming soon.” | Dispose works today. See the Warehouse Returns Workspace. |
| Support notifications bell | The in-app notifications bell is switched off. | Check your tickets directly in the Support area; you’ll see status changes there. |
| Warehouse map picker | The Google-map location picker on warehouse create/edit is off. | Enter the warehouse address in the form fields instead. |
Known limitations today
These work, but not the way the screen might suggest. Knowing them saves confusion.
- Dashboard headline tiles are placeholders. Sales, revenue and inventory-health tiles on the dashboard are not live numbers — trust Sales Reports for real figures.
- Notification delivery is still being completed. The Notifications settings save your preferences, but email / push / SMS sending is not wired up yet — the in-app experience is the source of truth. See Notification Preferences.
- Product video analytics are sample data. The numbers on the video analytics view are illustrative, not your real views yet.
- No variant matrix. One product is one offer — to sell colours and sizes you create separate products. See Selling Multiple Colors & Sizes.
- No bulk product upload. Products are added one at a time through the catalog-first flow.
- No single “seller score”. Performance is a set of honest signals, not one grade. See Understanding Performance Metrics.
- Return-dispute evidence isn’t stored. The dispute form’s image upload is not persisted yet — attach evidence to a support ticket instead.
When a button doesn’t work
- Check this page first — the feature may simply be coming soon or pending activation.
- If it’s flag-gated, use the “what to do instead” path above; the block is intentional, not an error.
- If it should work and doesn’t, look it up in the Error Code Index.
- Still stuck? Open a support ticket with a screenshot and your Store ID.