GloriaFood integrations and API: what keeps working until 2027 - and what to re-wire

Everything plugged into GloriaFood unplugs at the same moment: when the servers shut down on 30 April 2027, the API, the delivery-dispatch bridges, the POS connections, and the Stripe link all stop together. The services on the far end of those connections mostly survive - they're yours, or third parties with their own infrastructure. The work is mapping what's connected, knowing what carries over, and re-wiring in the right order.

First: map what's actually connected

GloriaFood claimed 150+ integrations, mostly via partner bridges, and many setups were wired once by whoever did the install and never documented. Thirty minutes now saves a bad day later - walk the admin panel and write down:

• Payments - the Stripe connection (and PayPal, if you paid for the connector)
• Delivery dispatch - Shipday, Tookan, Otter, ItsACheckmate, GetSwift, or another bridge sending orders to drivers
• POS - anything pushing online orders into your till (see the POS guide for that thread)
• The website embed - widgets and plugins on your own site
• Anything custom - if a developer ever touched the GloriaFood API for you, find out what they built; it dies with the API

What survives, what doesn't

Piece	After 30 April 2027
Your Stripe account, history, and payouts	Survives - it's yours; reconnects to any new platform
Your dispatch service account (Shipday, Tookan, etc.)	Survives - the service is independent; only the GloriaFood bridge dies
Your POS	Survives - the order feed into it doesn't
The GloriaFood API and webhooks	Gone with the servers
Custom code built against the API	Orphaned - needs rebuilding against the new platform

One structural note: GloriaFood never offered direct DoorDash, Uber Eats, or Deliveroo integrations - drivers came via the third-party bridges. If on-demand couriers matter to you, check how the replacement handles them natively rather than assuming parity with a workaround you'd built.

Re-wire in this order

• 1. Payments first. Connecting your existing Stripe account to the new platform is usually minutes, and nothing else matters until money flows
• 2. Delivery dispatch second - same service reconnected, or the platform's native delivery handling; test a real dispatch before cutover
• 3. POS bridge third, confirmed by name and tested with real tickets during parallel running
• 4. Custom API work last - scope it against the new platform's API early, build it once the basics flow

Storekit's integrations directory lists what connects out of the box; for anything custom, talk to us and bring your map from step one - it becomes the work order.

Frequently asked questions

Does the GloriaFood API stop working?

Yes - with the servers, on 30 April 2027. Anything built against it needs re-pointing before then.

What happens to my Stripe account?

Nothing. It's yours and reconnects to your next platform; only GloriaFood's link to it dies.

Does my delivery dispatch service survive?

The service does; the GloriaFood bridge doesn't. Reconnect or replace it during the migration.

Integrations are where migrations get surprised. Map yours this week and the re-wiring is a checklist, not an archaeology dig.