Skip to content

Platform Sync

Sync Uber Eats / Foodpanda delivery orders into the ledger — this is the main source of delivery revenue. Uber Eats credentials are captured by the browser Extension and synced by the server; Foodpanda is recorded via statement import instead.

Platform sync12

How sync actually works

A common misconception is that your computer has to stay on for sync to run. In fact the server fetches the orders; the Extension only hands your login over to it:

Browser ExtensionYour computerCaptures the merchant login onlyStoreOps serverFully automaticScheduled fetch, posted to booksUber Eats platformMerchant order data① Login infoStored encrypted② Scheduled fetchOrder dataLedger entries③ Posted automaticallyWorks with your computer off;log in again only when it expires

Connect Uber Eats (install the Extension)

  1. Install the StoreOps Chrome Extension and log in to the Uber Eats merchant portal in your browser.
  2. The Extension captures your login cookies and pushes them to the app (cookies only); once done the Uber Eats card shows a Connected badge.
  3. If credentials are absent or stale the badge shows Not set / Expired — log in to the merchant portal again to refresh them.

Credentials are stored encrypted and are never exposed in plain text.

The Extension version must match the app's required version. On a mismatch, Advanced / Debug shows Update to v1.5.1 recommended — update before syncing.

This page requires Manager permission; staff cannot open it.

Run a sync manually

  1. On the Uber Eats card pick a range: This month, This year, All or Custom (Custom lets you pick start/end dates).
  2. Click Sync now; the button shows Syncing… with progress, and on completion a toast reports how many orders were processed.

Sync now is disabled when there are no credentials, with the hint "Install the browser extension and log in to the Uber Eats merchant portal first".

Only one sync per store can run at a time; pressing it again while one is running is rejected.

Closed days are never overwritten by a sync, so later platform adjustments won't touch finalized books.

View status and run history

  1. The top of the card shows the Last sync time, the Next auto scheduled run, and the last result badge.
  2. Run history below lists each sync's Time, Platform, Status, Orders and Duration; statuses are Running / Success / Partial / Failed / Not run.
  3. Expand any row to see what was posted and the error message for any failed orders; failed syncs are retried automatically.
  4. Refresh (top right) updates the view; Clear history removes past run records (it does not affect posted data).

Foodpanda: use statement import

  1. On the Foodpanda card click Go to import to open the import page.
  2. Download the semi-monthly statement from partner.foodpanda.com and upload it on the import page to post the orders.

Foodpanda cannot be synced automatically by the server; it always goes through statement Excel import. Record the platform rental fee in Attachment 2 manually as an expense.