---
title: "Foodi Merchant App Order Management for Restaurants"
date: 2026-08-27
updated: 2026-08-29
lang: en
tags: ["delivery", "operations", "online-ordering", "reports"]
summary: "An operating SOP built directly from Foodi's published merchant-app functions."
canonical: https://rosuii.com/blog/foodi-merchant-app-order-management
author: "Rosuii Team"
---

# Foodi Merchant App Order Management for Restaurants

An operating SOP built directly from Foodi's published merchant-app functions.

**Last verified: 2026-08-28**

Foodi merchant app order management covers accepting or rejecting orders, viewing order history, checking performance, switching items and add-ons on or off, reviewing business hours, downloading delivered-order reports, receiving inbox updates and reaching the Help Centre. Those functions are documented in Foodi's merchant guideline.

The app works only when a restaurant assigns decisions. Every shift needs an order owner, an availability owner and an escalation route.

## Function-to-owner map

| Function | Shift owner | Control |
| --- | --- | --- |
| New order | Counter or expeditor | Accept only after capacity check |
| Reject | Shift lead | Use valid reason |
| Availability | Kitchen lead | Switch item/add-on promptly |
| Business hours | Manager | Verify before service |
| Order history | Supervisor | Search by ID/date |
| Delivered report | Accounts | Download and reconcile |
| Inbox/help | Manager | Record action and issue ID |

## New-order SOP

Keep the merchant device powered, connected, audible and visible. On a new order, check item availability and realistic preparation capacity before accepting. Send the confirmed ticket to the correct kitchen and packing station.

If the store cannot fulfil reliably, use the current official control available to the account instead of accepting and cancelling later.

## Availability discipline

The guideline says items and add-ons can be switched on or off for different periods. Review high-risk stock before opening and after each rush. Switch off the exact unavailable item or add-on, not an entire category unless necessary.

Record who changed availability and when. Restore only after stock and preparation capacity are confirmed.

## Handover and rider flow

- Match order ID to package
- Check every item and modifier
- Seal and label without exposing private data
- Record ready time
- Confirm rider handover status
- Keep disputed package evidence
- Escalate delay through the official help route

## Reports and reconciliation

Foodi's guideline says merchants can choose a date range to view or download delivered-order data. Use it to match restaurant POS entries, Foodi settlement evidence and bank deposits.

Performance screens help operations, but finance should retain the source report, invoice and bank proof for the period.

## App versus API

The merchant app is the restaurant's direct operational interface. Foodi's Partner Gateway separately describes approved catalogue and order integration through credentials, staging and testing.

Do not run both manual and integrated entry without a duplicate-control design. Confirm the source of truth for status, menu and reports before launch.

## Verify the current partner workflow first

Merchant app screens, onboarding requirements and commercial terms can change. Use the restaurant's current Foodi partner material, executed agreement and authenticated account as the authority for enabled functions. This guide describes an operational control pattern; it does not claim that every account has the same buttons, reports or integration access.

Create a function register showing order acceptance, preparation estimate, availability, cancellation, rider handover, support, settlement report and user access. Mark each as available, manual, restricted or not confirmed, with the verification date and account owner.

## Design the order-desk handoff

Avoid several phones responding independently to the same alert. Name a primary device or order desk and a backup route. The person accepting an order needs a clear view of branch availability and kitchen capacity, not only permission to press accept.

| Event | Primary owner | Control |
| --- | --- | --- |
| New order | Assigned order desk | Alert acknowledged once |
| Acceptance | Authorized role | Menu and capacity checked |
| Kitchen release | Production role | Stable order ID on ticket |
| Ready state | Handover role | Actual package is complete |
| Rider pickup | Handover role | Order ID and package matched |
| Exception | Shift manager | Reason and support case recorded |
| Close day | Finance/manager | Orders and settlement inputs exported |

## Keep menu and availability disciplined

Map marketplace item names to the restaurant's internal item and kitchen identifiers. Review price, description, variants, add-ons and preparation constraints after every approved menu change. When a product is unavailable, use the current supported availability control and record the branch and expected duration.

Do not repeatedly accept an unavailable item and resolve it through customer calls. Review cancellations and substitutions by item to find mapping or availability failures. Screenshots are useful evidence, but the menu source and platform publish status should remain the control record.

## Handle cancellation and support cases with evidence

Record the marketplace order ID, restaurant order ID, event time, factual reason, support reference and resolution. Distinguish customer, restaurant, rider, payment and system causes rather than grouping every failed order as cancellation. Do not infer who bears a charge without the applicable agreement and case result.

Protect customer data in support screenshots. Include only the fields needed to locate the order, redact unrelated contact or payment details and store the case in an access-controlled location. Review repeated causes weekly and change the menu or handoff process where the evidence points.

## Daily reconciliation checklist

The merchant order screen is an operational view, not automatically a complete accounting ledger. Use the current official report and contract definitions for settlement. Do not hard-code one commission percentage because account packages and adjustments may differ.

- Export or record all orders for the service day
- Match accepted, cancelled and completed classifications
- Map marketplace IDs to restaurant order IDs
- Separate gross item sales, discounts, fees and adjustments
- Record refunds and support decisions
- Compare payment or payout period with order period
- Investigate unmatched and duplicated records
- Lock the reviewed file with owner and date

## Merchant-account access review

Give each staff member the narrowest role the current partner system supports and avoid sharing one credential across counter, manager and finance users. Record the business owner of the account, recovery channel and approved devices. Remove access promptly when a role or employment relationship changes.

Review access and notification routing after every staffing change and on a defined schedule. A deactivated internal POS user may still retain marketplace access if the systems are separate, so offboarding must cover both. Preserve account-change and support evidence without storing passwords or OTPs.

The merchant app becomes reliable when every button has an owner and an evidence trail. Train the full shift on order, availability, handover and support before adding volume.

## Related guides

- [Foodi Restaurant Partner Onboarding](https://rosuii.com/blog/foodi-restaurant-partner-bangladesh)
- [Restaurant Waiter Ordering App](https://rosuii.com/blog/restaurant-waiter-ordering-app)
- [Delivery Marketplace Integration](https://rosuii.com/blog/integrate-foodpanda-pathao-restaurant)
- [Compare restaurant management software](https://rosuii.com/compare)

**See this workflow in Rosuii:** [Connect restaurant order and kitchen workflows in Rosuii](https://rosuii.com/features)

## Sources checked

- [Foodi merchant app guideline](https://cdn.foodibd.com/Maintenance/MarchentAppGuideline.pdf)
- [Foodi Partner Gateway API documentation](https://integration.foodibd.com/)
- [Foodi official website](https://foodibd.com/)

[Start using Rosuii for free](https://rosuii.com/register)

## FAQ

### What can the Foodi merchant app do?

Foodi documents order processing, order history, performance, menu availability, hours, delivered-order reports, inbox and help-centre functions.

### Who should accept Foodi orders?

A named counter or expeditor role with current kitchen-capacity and item-availability information.

### Can unavailable items be paused?

The official guideline says food items and add-ons can be switched on or off for periods of time.

### Can reports be downloaded?

The guideline says delivered-order data can be viewed or downloaded by selected date range.

### Is the app the same as API integration?

No. API integration is a separately approved technical workflow with credentials, staging and testing.

### Does every Foodi merchant account have the same features?

Do not assume so. Verify functions, reports and permissions in the current authenticated account and partner material.

### Who should accept marketplace orders?

Assign a primary order-desk role with menu and capacity visibility, plus a documented backup rather than several independent responders.

### Can the merchant app replace settlement reconciliation?

Use the current official reports and agreement definitions; an operational order screen may not contain every fee, adjustment or payout detail.

---
Canonical: https://rosuii.com/blog/foodi-merchant-app-order-management
Machine-readable site overview: https://rosuii.com/llms.txt