Do I have to stop using Foodics?
No. Foodics keeps taking orders and printing receipts; Aqid ERP keeps the books, the VAT return and payroll.
Foodics stays where it is strongest, taking orders at the till. Aqid ERP keeps the books: each business day's Foodics orders come in as one cash invoice per branch, beside purchases, stock counts, the VAT return and payroll. A shop that sells items, not dishes, can use Aqid ERP's own till instead.
Generate an API token in the Foodics console and paste it into Aqid ERP's sales channels. Orders are read per business day and per branch, with returned and void orders left out of the sale. A POS is paid at the till, so there is no payout to match, and since Foodics issues the receipts, Aqid ERP books the day's invoice without reporting it to ZATCA again.
For items with a barcode and a price, not dishes: the till in the browser reads barcodes, sells offline and closes each session with a cash count, and every sale is already in the books. It has no tables, kitchen screen or modifiers, so a restaurant keeps Foodics.
Foodics has its own accounting module, Foodics Accounting, which its site says posts journal entries from the POS and handles VAT filing. Moving the books to Aqid ERP is worth it for what sits beyond the till: purchasing with approval limits, stock across warehouses with landed cost, payroll, and several companies under one login.
No. Foodics keeps taking orders and printing receipts; Aqid ERP keeps the books, the VAT return and payroll.
With a Foodics API token, Aqid ERP reads each business day's orders per branch and books one cash invoice per branch, paid into the account you choose. Until the connection is checked on your account, compare its first days with Foodics' sales report.
No. Foodics issues and reports the receipts at the till, so the daily invoice from Foodics is booked in Aqid ERP as already reported: numbered and posted, not sent to ZATCA again.
Set up for Saudi Arabia's rules from the first day.