14-day restaurant trial: what to test before switching

What does the trial actually include?

Day 1: check access before entering data. Nexara starts with 14 days of Growth, then drops to Free unless you choose a paid plan. Signup uses a phone number and an SMS code, with no card or commercial registration required. You can cancel anytime and nothing auto-renews.

Growth includes one printer. Call Center is a Pro feature, so a phone-order test requires separately confirmed Pro access or a demonstration. Check access before assigning tests to staff.

QR dine-in starts on Growth and is included in the trial. Free does not include QR dine-in.

Free supports one branch, 20 products and a branded ordering site. The site carries the Powered by Nexara badge. Free allows 30 website orders a month, with no printers or Call Center access. QR dine-in eligibility starts on Growth.

Day 2: write your acceptance sheet. For each test, record the expected result, what happened, who checked it and whether a repeat passed. Nexara handles the order and operations layer; your till and any tax-invoicing requirement stay separate.

• Use staff-controlled contact details for test customers.
• Agree how test orders will be identified and kept separate from real sales.
• Record the plan and access level used for each test.
• Record unavailable features as pending rather than passed.

Can staff trust the menu?

Day 3: build a representative menu. Include an Arabic item name and an item with modifiers, such as a sandwich with an extra topping. Nexara supports products, categories and modifier groups. Enter your actual prices privately, then compare the order screen against the menu your staff use.

Check the base price separately from the modifier price. Read the Arabic names with the person who prepares the food. A saved item name can still be too vague for a kitchen ticket.

Day 4: test availability and channel visibility. Nexara has per-branch availability and menu channels that control which menu a channel sees. Make a test item unavailable, then inspect the relevant ordering page. Restore it and check again. Check the customer-facing page as well as the editing screen.

Where your plan supports additional branches, verify each branch separately. A change at the wrong branch is a failed test.

Complete one staff-controlled checkout on your own Nexara storefront. Use the SMS code, add an item and modifier, and compare the totals with your acceptance sheet. Check the delivery charge where relevant, confirm the assigned branch, inspect the kitchen ticket and open the customer tracking link. This test works without marketplace approval or Pro access.

Will a kitchen ticket survive a printer failure?

Day 5: connect the printer you intend to keep. Nexara prints on standard ESC/POS thermal printers over USB or network using its desktop printing app. Windows is the primary setup. Bluetooth printing is not supported. Test your actual device and connection.

Print an Arabic item with an Arabic modifier, then a bilingual ticket. Nexara supports Arabic and English on the same ticket. Check joined letters and whether the modifier is visibly attached to the correct item.

Day 6: interrupt the printer connection in a controlled test. Outside service, create a clearly identified test order while the printer is unavailable. Confirm that the order stays on the board and its ticket waits in the print queue. Restore the printer and check that the expected ticket prints once.

Day 7: interrupt the branch internet connection. Orders can continue arriving in the cloud while the branch is disconnected, and printing catches up after reconnection. Test a phone hotspot beside the printer PC as your backup. Check whether staff can restore the connection without help.

How do I check that orders reach the right branch?

Day 8: arrange a supervised Talabat test. Keep fictional orders out of the live marketplace. Nexara receives Talabat orders, matches outlets and menu items, handles incoming cancellations and sends order status updates back to the provider. Agree on a test arrangement with your implementation contact before sending anything.

1. Prepare a fictional basket using products in your test menu.
2. Have the implementation contact confirm the intended outlet and product mappings.
3. In the agreed test arrangement, inspect the incoming order, its branch and its kitchen ticket.
4. Check cancellation handling and the provider status response where testing access permits.

A manually entered copy tests the kitchen workflow; verifying Talabat intake requires an order through the actual connection. Talabat and Careem activation depends on partner approval, so mark intake as pending if approval is missing. See Talabat and Careem order intake for the distinction between marketplace orders and own-order delivery dispatch.

Day 9: test a phone order with confirmed Pro access. Ask a colleague to act as the caller using staff-controlled details. Nexara's Call Center looks up customers by phone and shows saved addresses and past orders. Have the order taker confirm the address and branch before submitting. Without Pro access, mark a demonstration as watched rather than tested by staff.

Day 10: scan a table QR code as a guest. Enable dine-in on the branch, generate its table code and order from a phone. Confirm the ticket carries the correct table number. Nexara supports shared bills split by claimed items; test that if your floor team needs it. Dine-in uses pay at the table, while online card payment is hidden to prevent double payment on a shared bill.

Do the reports match the orders?

Day 11: reconcile the test orders. Write down the expected amount for every test order, including one cancellation. In the End of Day report, compare expected gross sales, the cancelled order and the resulting net figure. In Cashier Reconciliation, compare the expected payment totals for cash, card or other tested methods with the report totals. Then compare the final net-sale figure with the till's closing net-sale figure for the same branch and reporting period. Match every amount back to its order and kitchen ticket before accepting the result.

Keep the branch and reporting period consistent. Trace any difference to the individual order before calling it a reporting error. Ask the closing cashier to repeat the check.

Day 12: test permissions with a staff login. Nexara supports user-to-branch assignments and permissions, so use the person's intended role to check what they can see and change. Then have them find a test order using Order History search or filters.

Nexara's FAQ promises CSV export of orders and customers. Request a sample export and inspect it before switching. Confirm that you can retrieve the records your restaurant needs.

Days 13 and 14: What earns a switch decision?

Day 13: repeat every failed test. Preserve the original result and note what changed. For an intermittent printer fault, repeat the conditions that caused it. Nexara offers support through WhatsApp and email on Amman hours, in Arabic and English. Issa Al-Dalu, founder of Nexara, answers support himself.

Day 14: choose the operating setup and plan. Nexara has a free plan, then paid plans per branch in Jordanian dinar. Current rates are one WhatsApp message away through Nexara's contact page. Check which tested features would become unavailable after the Growth trial. Continuing the printer and dine-in setup requires a suitable paid plan.

Move only the tasks your team has passed. Keep the current marketplace intake route until approval and testing are complete. Use the one-day go-live checklist to plan the handover.

Start the Nexara trial at nexaratech.io using the signup button below. You will open the account with your phone number and an SMS code, without a card.