tawlat

Switching

Bring your restaurant onto tawlat, without losing a beat.

Whether you're switching from Foodics, Odoo, Oracle Micros, a homegrown ERP, or just receipts in a drawer, tawlat is built to absorb your existing menu, customer book, order history, and supplier list, and put your team on a unified system the same week. No data left behind, no commission on direct online orders, no contract.

  • Live within 2 to 7 days
  • Take a final export before cutover
  • No contract, monthly billing, cancel anytime

What stays the same

  • Your menu

    Items, categories, modifiers, prices, and recipes load into tawlat with the same structure your team already knows.

  • Your customer book

    Phone numbers, addresses, last-order context, and any wallet balances come across cleanly, indexed for instant lookup.

  • Your accounting

    Z-report at close, daily and monthly summaries, VAT breakdowns, service charge, all in formats your accountant already reads.

  • Your suppliers

    Supplier book, open purchase orders, payment terms, and ingredient links are imported alongside your menu.

What gets better

  • One unified system

    Terminal, kitchen display, cashier, hostess, online menu, admin, all on the same live data. No more juggling PoS plus KDS plus spreadsheet.

  • Local invoicing

    JO and GCC tax rules and invoice formats built in. No exports, no plugins, no "we'll figure that out later."

  • Mobile-first admin

    Run your restaurant from a phone, live orders, driver settlement, daily close, audit log, all on one screen from anywhere.

  • Bilingual, properly

    Every workstation switches between English and Arabic at the user level. RTL is built in, not bolted on.

Where are you switching from?

Pick the closest match to your current setup. Each one opens a dedicated page covering the quirks of that system, what we've seen break in past migrations, and how tawlat handles it.

What comes across with you

tawlat is built to be the new home for the data you already have, not a fresh start. Here's what we import in a typical migration.

  • Menu, modifiers, recipes

    Items, categories, modifiers, sale prices, and the recipe map (ingredients per dish) imported with their current relationships.

  • Customer book

    Phone numbers, names, addresses, last-visit context, loyalty status, and wallet balances, indexed for instant lookup.

  • Order history

    Up to 24 months of historical orders, so reports, customer profiles, and supplier reconciliations work from day one.

  • Supplier book & open POs

    Suppliers, contact details, ingredient links, open purchase orders, and payment terms move over together.

  • Staff, roles, permissions

    Your existing roles map to tawlat's permission groups. Manager-only actions stay manager-only on day one.

  • Tax & accounting settings

    VAT rate, service charge, payment-method mix, and report templates configured to match your accountant's existing process.

How the switch actually works

Three phases, roughly one week, and one quiet shift for the cutover. Your existing system keeps running the whole time.

  1. 01

    Audit & mapping

    Day one. You share an export from your current system. The tawlat team maps every field to the new schema, flags any gaps, and confirms the timeline with you. Custom fields, unusual modifiers, and one-off workflows are caught here, not on cutover day.

  2. 02

    Parallel import

    Days two to three. Menu, customers, history, and supplier data load into tawlat in the background while your old system keeps running every shift. Your team trains on real data, on the workstations they'll actually use.

  3. 03

    Cutover, one shift

    Pick the quietest service of the week. The team switches to tawlat, the old system retires, and you're live, end to end. Before cutover, you'll take a final export from your old system as a safety net for historical lookups.

Frequently asked questions

If something's not here, the easiest path is a 5-minute call. We've seen most of the edge cases.

  • Will I lose any data during the switch?

    No. Your existing system keeps running the whole time, and tawlat imports menu, customers, order history, supplier book, and tax settings in parallel. Anything that doesn't map cleanly is flagged in the day-one audit, not on cutover day. Before cutover, you'll take a final export from your old system to keep on hand as a safety net.

  • How long does the migration take?

    Most restaurants are live on tawlat within 2 to 7 days of the first call. The cutover itself happens during one quiet service. The longest part is matching your existing menu structure (items, modifiers, recipes) to tawlat's model, usually done in a single workshop with your chef and accountant.

  • Do I sign a contract?

    No. tawlat is monthly, cancel anytime. Migration is included in standard onboarding, there's no separate migration fee and no annual commitment.

  • What if my current system has custom fields or unusual workflows?

    Almost every restaurant does. The day-one audit exists for exactly that. tawlat's schema covers the vast majority of restaurant setups in MENA, but anything custom (internal codes, custom loyalty rules, supplier-specific terms) is mapped manually together with your team before cutover.

  • Can I run tawlat alongside my existing system?

    Yes, that's the default. Parallel running is the whole point of the import phase. You only cut over when your team has trained on real data and you're confident. Before cutover, you'll take a final export from your old system so you have full history on hand.

  • What does my accountant need to do?

    Very little. tawlat exports daily, weekly, and monthly summaries in the formats your accountant already reads (Excel, PDF, CSV). Z-report, VAT summary, payment-method breakdown, and supplier reconciliation are all ready out of the box. We can also share a sample export ahead of cutover so nothing's a surprise.

  • What if I'm coming from paper and WhatsApp, with nothing to export?

    That's the biggest jump, and the most rewarding. The starting point is a short workshop to capture your menu, top customers, suppliers, and prices, then tawlat goes live the same week. Your operations don't need to wait for a perfect dataset, the system is designed to grow with what you add over the first few shifts.

Not sure where you're switching from?

Show us your current setup in a 15-minute call, and we'll walk through how the move works for your specific system, what comes across, what to plan around, and how soon you can go live.

Book a switching callSee pricing