Yonoton is a food-ordering and POS-commerce platform. The Mobal–Yonoton integration keeps a profile's opening hours in sync automatically: Mobal pulls the latest hours from Yonoton on a daily schedule and whenever you reconnect, then pushes them downstream to directories like Google and Apple. This article explains what is synced, how the sync works, and what to check when something goes wrong.
What Gets Synced
The integration syncs opening hours only. It does not sync menus, prices, orders, or any other business information.
Data type | Synced? |
Regular (weekly) opening hours | ✅ Yes |
Special / holiday hours | ✅ Yes |
Menus & products | ❌ No |
Prices & orders | ❌ No |
Other business info (name, address, etc.) | ❌ No |
When special hours are synced, any existing Mobal special hours for those same dates are replaced by the Yonoton values.
How the Sync Works
The sync is one-way: Mobal reads from Yonoton. Nothing in Mobal is ever written back to Yonoton.
Synced hours are automatically pushed downstream to connected directories (Google, Apple, etc.) as part of Mobal's normal profile update flow.
When does a sync run?
Daily at ~19:00 UTC — an automatic scheduled sync runs for all connected profiles. This runs before Mobal's main directory sync (~20:00 UTC), so downstream platforms always receive the freshest hours.
On connect — hours are pulled immediately when a profile is first connected to Yonoton.
On-demand — a manual "resync hours" action is available in the Integrations section of the profile.
How a Profile Is Connected
Each Mobal profile is connected to one Yonoton site via an API key. A single Yonoton site can only be linked to one Mobal profile at a time.
For step-by-step setup instructions, see How to Connect Yonoton to Your Mobal Profile.
Troubleshooting for CS
Hours are no longer updating
The most common cause is an expired or revoked Yonoton API token. Mobal sets a re-authorization-required flag on the integration when the token becomes invalid. Check the profile's Yonoton integration status — if the flag is set, the customer needs to reconnect using a new API key.
You can also inspect the integration's sync logs: on success they record the Yonoton payload; on failure they record the error details. These logs are accessible on the profile and are the fastest way to diagnose what went wrong.
"Site already in use" when connecting
Each Yonoton site can only be connected to one Mobal profile at a time. If the customer sees this error, the site is already linked to another profile. Identify which profile holds the connection and disconnect it before trying again.
No sites listed when connecting
If the site picker is empty, the API key does not have access to any sites in Yonoton. Ask the customer to verify the key's permissions in their Yonoton account settings, then reconnect in Mobal.
When to escalate to Engineering
The sync log shows a successful API call but the hours in Mobal are still wrong.
A profile's sync status appears stuck (shows as running but never completes).
Any error not covered by the scenarios above.
Need help? Contact us at [email protected].