POS with GrabFood and ShopeeFood integration in Vietnam

What the connection does

LOOP POS brings GrabFood, ShopeeFood and Be orders into one kitchen queue in Vietnam. The purpose is to connect incoming platform orders with the venue's preparation workflow, so kitchen staff can work from an agreed operating view. It is not a new delivery marketplace and it does not replace the restaurant's merchant account. The platform remains responsible for its own merchant terms, delivery arrangements and charges. Confirm the actual connection available to your outlet before treating this description as an opening-day requirement.

An order connection and a settlement record are different things. Seeing an order in the kitchen queue does not prove that a platform payout has arrived in the bank, that a promotional deduction is correct or that a cancelled order has been refunded. Keep the merchant statement available for financial reconciliation. This page establishes the confirmed order-ingestion scope, not a promise that every menu action, payout field or platform exception is automated. Delivery order ingestion outside Vietnam is on roadmap.

Prepare the outlet before setup

1. Identify the outlet's active merchant account for each platform and the person authorised to manage it. Confirm connection eligibility, credentials and any platform approvals with LOOP POS support. Do not share private passwords in a public document or assume another branch's account applies to this location.
2. Compare the menu names, sizes, toppings and notes in the POS with the platform menu. Make a record of mismatches before testing. An apparently correct item name can still hide a different portion, included modifier or selling price, so use the actual products your kitchen prepares.
3. Agree how the kitchen will distinguish delivery orders from counter or table orders. Review the station that prepares each item and the person who checks the finished order. Keep packaging, included utensils and customer notes in the operating checklist rather than assuming the connection supplies every instruction.
4. Arrange a test period with support and the outlet team before relying on the connection during peak service. Keep the existing merchant workflow available as a fallback until the team has checked the result. No guaranteed activation duration or platform approval time is published here.

Test one complete order

Place a test order through the platform that has actually been connected. Check that it reaches the intended outlet and appears in the kitchen queue once. Compare item quantities, modifiers, notes and the order reference with the platform record. The kitchen should confirm what it will prepare and how the finished order is identified for collection. Record any missing field and resolve it with support before treating the test as successful. A screenshot of an incoming ticket alone does not verify the complete service process.

Follow the order through the venue's own handover and closing routine. Ask the cashier and kitchen to identify the same order without relying on memory. Check whether an operator could accidentally enter it again from the merchant screen, and document how duplicate entry is prevented in the agreed workflow. This is a verification checklist, not a claim that every duplicate or collection event is automatically handled. Repeat the relevant test when the outlet account, menu or operating arrangement changes.

Check cancellations, stockouts and exceptions

Before live service, confirm the handling of a cancelled order with support and the platform. The team needs to know whether preparation should stop, who acknowledges the cancellation and which record is used for the financial review. Do not assume a kitchen action cancels a platform order or reverses its charge. The restaurant's merchant terms govern those events. Preserve the platform reference and the outlet's record when reporting a discrepancy, while keeping customer information restricted to the staff who need it.

An unavailable item needs an agreed process as well. Confirm how the outlet marks it unavailable on the merchant platform and what happens to an order already received. Do not claim automatic stockout propagation, menu publishing speed or refund behaviour unless that exact connection has been verified. If an order does not reach the kitchen queue, use the fallback procedure agreed before service and report the missing order with its platform reference. The connection does not remove the need for a responsible person at the outlet.

Reconcile and confirm plan limits

At closing, compare platform orders with the outlet's recorded sales for the same period. Review cancellations, promotions, fees and settlement timing against the merchant statement rather than assuming the gross selling amount is the money received. Keep currency and trading periods consistent. A delivery commission estimate elsewhere on a page is not your signed merchant contract. Where records disagree, investigate the specific order and deduction before changing prices or reporting a margin improvement.

Check the current LOOP POS price list and confirm which connection scope is available for the venue. Do not assume every integration is included in Free or that a single approval covers every branch. Ask about the required plan, supported outlet account and ongoing support responsibilities before rollout. Loyalty and CRM are handled by the separate PEKO product. PEKO customers get 50% off LOOP POS paid plans. Order ingestion does not file the venue's tax declarations or pay tax on its behalf.

LOOP POS plan prices

Confirmed Vietnam feature scope

Evaluate forecasts with your own sales

Frequently asked questions