Migrating from Foodics to Nexara: what transfers, what does not
Your cook calls across the counter: the extra cheese is on the Foodics order, but missing from the kitchen ticket. Before changing systems, test that the whole order reaches the kitchen.

Nexara gives you an order layer beside the till as a restaurant order and operations platform built in Amman, Jordan. It does not offer JoFotara e-invoicing. To migrate from Foodics, preserve your records, rebuild and test the menu, check printer compatibility, then agree the channel cutoff with Nexara.
Are you replacing Foodics, or changing the order layer?
Foodics provides restaurant POS software. Nexara handles orders and operations beside the till, with phone ordering on the Pro plan. If phone orders are moving, include Pro in the scope and write down how the cashier will record those sales at close.
Assess Nexara when the problem is gathering orders into a branch queue and getting readable tickets to the right printer. A direct Foodics-to-Nexara connector is outside the confirmed migration scope, so keeping Foodics as the till requires an agreed daily handoff.
| Requirement | Foodics | Nexara |
|---|---|---|
| A restaurant POS at the counter | The better fit for this requirement; Foodics provides restaurant POS software. | An order and operations layer beside the till. |
| Continue using existing Foodics records | Keeping access avoids a historical-data migration. Confirm your account and contract terms. | Preserve Foodics records separately and establish a cutoff for new Nexara records. |
| Gather incoming orders for the kitchen | Check your current Foodics package and activated integrations. | One branch queue supports Talabat, Careem, phone, website, app and table QR orders, subject to setup and plan. |
| Operate without an internet connection | Confirm the exact behaviour of your Foodics setup. | Orders keep arriving in the cloud while the branch is disconnected; the board needs internet and printing catches up after reconnection. |
The Foodics and Nexara comparison covers the broader choice. For this migration, make a written boundary: what stays at the till and what moves to Nexara.
How do you export the Foodics menu and rebuild it?
Ask Foodics support or your account administrator how to export the menu from your current account. Confirm which fields the available export contains, then save the file with its export date and the branch or menu it covers.
Nexara supports products, categories, modifiers and modifier groups, with per-branch availability and channel-specific menus. Use those fields to organise a working copy of the export for a checked rebuild.
- Save an untouched copy of the source file. Keep any item identifiers it contains so similarly named products are not confused.
- Prepare a working sheet with Arabic and English names, prices, categories, modifier choices and branch availability. Mark anything missing from the export.
- Map each item into Nexara's menu structure. Flag required choices and unusual pricing rules for explicit testing.
- Check the rebuilt menu against the source. Place test orders with modifiers and try ordering unavailable items, then inspect accepted orders and their printed tickets.
Keep aggregator publication separate from menu entry. Nexara supports catalogue work with Talabat and Careem. Check outlet mapping and verify the published menu on the intended marketplace outlet before staff begin accepting orders through the new setup.
What happens to customers and old sales history?
Nexara stores customer records with addresses and order history. Preserve your existing Foodics records separately, and have a sample file reviewed before agreeing which data will be entered into Nexara.
- Customers: request the export options available to your Foodics account. Review phone-number formatting and duplicates before agreeing any transfer.
- Historical orders: retain accessible copies in the formats Foodics makes available. Tell staff where to look up tickets issued before the cutoff.
- Refunds and unsettled payments: document where each open case must be completed. Keep the original transaction reference with the case.
- Inventory: Nexara supports ingredients, recipes and stock counts. Automatic transfer of Foodics stock history or recipes is outside the confirmed migration scope, so agree opening quantities separately.
Ask Foodics about record access after cancellation before ending the contract. Keep the migration cutoff with your archive so later comparisons have a clear boundary. Nexara offers order and customer CSV export for records you build in the platform.
Can you reuse the hardware and thermal printers?
Nexara runs in a browser and uses the Nexara Printing desktop app, with Windows as the primary platform. It drives standard ESC/POS thermal printers over USB or network. Test your existing printers with the intended computer before deciding what hardware to replace.
Record each printer's exact model and connection type. Check that the intended computer can run Nexara Printing and reach the printers, including any installation restrictions on a locked terminal. Bluetooth printing is not supported.
Print an Arabic item with Arabic modifiers during the test. Nexara supports readable Arabic thermal tickets with English on the same ticket. Check category routing as well: a legible ticket at the wrong station is still a failed test.
Printing starts on Growth, which includes one printer; Pro supports unlimited printers. Free and Starter do not include printing. Use the thermal printer compatibility guide to prepare the hardware check.
What should happen on the day of the switch?
Nexara's ordering link can go live on signup day, and a compatible printer usually prints the same day. Talabat and Careem activation depends on partner approval. Set the switch date around confirmed channel readiness and completed menu tests.
- Freeze menu edits at an agreed time. Save the final source copy and assign one person to approve later changes.
- Finish or explicitly assign every open order. Record which system owns pending deliveries, cancellations and refunds.
- Test each channel you intend to activate. Verify the branch, item choices, payment status and printed output against the original order.
- Agree the aggregator cutover with the relevant partner. Make clear which system handles acceptance and status updates so staff do not process the same order twice.
- Brief the shift team. Each person should know where orders arrive, where cash is recorded and who decides whether to pause the switch.
- Keep a fallback procedure. Provide an internet backup and retain the old workflow until the responsible manager accepts the new setup.
Keep a phone hotspot beside the printer computer and test connecting to it before service. Give the shift manager responsibility for switching connections and checking that waiting tickets have printed.
At close, check channel totals against the records each channel provides. The cashier records the day's net sale for reconciliation. Nexara provides a cashier reconciliation report; automatic payment matching is not available.
What must be agreed before you commit?
Write an acceptance sheet covering menu accuracy, printer routing, channel activation and archive access. Name whoever signs off each area. Nexara does not offer accounting or ERP connectors today, so assign those duties to the systems that will continue handling them. Review payment settings separately rather than including them in an assumed automatic transfer.
Nexara offers a free plan plus paid plans per branch in JOD, with current rates on request through the pricing FAQ answer. Match the plan to the actual workflow, including QR dine-in, which starts on Growth. Support is available through WhatsApp and email on Amman hours, in Arabic and English.
For a migration scope review with Nexara at nexaratech.io, send founder Issa Al-Dalu a sample menu export without customer data, your printer models and a note explaining what you want to keep at the till. Use the WhatsApp conversation to agree the setup scope before choosing a switch date.
What to remember
- Decide what the till keeps and what moves to the order layer before any export.
- Treat Foodics exports as source records for a checked rebuild.
- Test Arabic tickets and every activated order channel before cutover.
- Preserve historical records and agree who handles unfinished transactions.
Questions people ask
Can Nexara automatically import my Foodics menu?
Plan for a checked menu rebuild using your Foodics export as source material. Confirm the setup method after a sample file review.
Will my old Foodics customers and orders appear in Nexara?
Keep old records accessible separately and confirm any customer-data entry after a sample review. Automatic historical-order transfer is outside the confirmed migration scope.
Can I keep Foodics as my till and use Nexara for orders?
Nexara is designed as the order and operations layer beside the till. Agree how staff will hand off orders and reconcile sales between the two systems.
Can I keep my existing kitchen printers?
Possibly, if they support standard ESC/POS over USB or network and pass testing with Nexara Printing. Check the exact models before buying replacements.
Does switching to Nexara remove Talabat or Careem commission?
No. Nexara charges no commission on your own ordering channels, but Talabat and Careem retain their commission on orders they bring.
When is staying with Foodics the better choice?
Stay with Foodics if your main need is its restaurant POS workflow and it already serves you well. Assess Nexara for a specific order-handling problem beside the till.