Retail ERP Consultant, Saudi Arabia

E-invoicing at the till: what a Saudi retailer must verify

E-invoicing in the Kingdom, administered by ZATCA, applies to retail sales as well as business-to-business invoices. Consumer sales are generally issued as simplified tax invoices, which carry their own content rules such as a QR code, while sales to registered businesses may need a standard tax invoice. Requirements for integration with the authority have been introduced in stages, so check your own obligations with your tax advisor rather than relying on a vendor's general statement.

For the POS, that turns into a list of questions I take into every demo:

• Does the POS generate compliant invoices itself, or rely on the ERP or a separate e-invoicing connector?
• What happens when a branch loses connectivity? How are invoices issued offline and reported when the link returns?
• How are returns and exchanges documented, and do credit notes reference the original invoice correctly?
• Can the till switch to a standard invoice when a business customer asks for one?
• Who supports the connector when the authority updates its requirements?

I build these into the fit-gap analysis and UAT scripts. The Saudi ERP consultant page covers e-invoicing for the wider finance function.

Arabic-first receipts and an item master that supports them

Arabic is the main language at the till for most shoppers, so receipts, refund slips, vouchers and shelf labels are designed Arabic-first, often with English alongside for brands that serve a mixed customer base. That starts with the item master. Every sellable item needs a proper Arabic name, not a transliteration typed at the last minute, and descriptions short enough to fit a receipt line.

Variant-heavy categories such as fashion and footwear need care, because size and color attributes must also read correctly in Arabic. Promotions printed on receipts, such as a bundle discount or a loyalty redemption, need agreed wording in both languages.

Hijri dates appear in some documents and customer communications, while systems usually work internally in Gregorian dates. I decide with your team where each calendar is shown and make sure reports for management use one consistently.

Finally, I test physical output. Right-to-left text, mixed Arabic and English lines and QR codes have to print clearly on the thermal printers already in your branches. Printer tests belong in UAT, because a receipt that a shopper cannot read creates questions at the counter on the first trading day.

Supplying branches across the Kingdom

A Saudi store network can span very long road distances between regions. Many retailers keep a central warehouse near their head office and one or more regional hubs, with trucks serving branches on scheduled routes. Stock spends real time in transit, and branches in smaller cities may be supplied less often than those near the hub.

The ERP design needs to reflect that. Stock in transit should be a visible location, not a gap between two warehouses. Replenishment rules for distant branches need longer cover than branches next door to the warehouse. Transfers must be confirmed on receipt, with discrepancies raised immediately rather than at the next count.

I map the supply network, delivery schedules and receiving practice per branch type, then define allocation and top-up rules with your merchandisers. For larger networks I also look at whether some branches should transfer surplus stock to each other within a region instead of returning it to the center.

The warehouse side itself is covered on my Odoo Inventory page for Saudi businesses, so this page stays with what branches need.

Tender mix, settlements and branch profitability

A typical Saudi till takes mada debit cards, international credit cards, digital wallets, buy now pay later plans and still some cash. Each tender settles differently: card acquirers pay out net of fees on their own cycle, buy now pay later providers settle in batches with their own fee and refund rules, and cash has to be counted, deposited and matched.

When the POS only posts a daily total, finance spends its mornings matching statements by hand. I design the cash-up so each branch's takings are recorded by tender, settlements are imported and matched automatically, and only differences go to a person. Refunds on buy now pay later purchases get specific attention, because the money flows back through the provider rather than the till.

Branch profitability then brings in rent, staffing and shrink by branch. Many stores sit in malls whose leases may include sales-linked rent, so a clean branch sales figure helps there too. I set branch, region and brand dimensions in the chart of accounts with your finance lead and agree how shared costs are allocated, so regional managers can compare branches fairly.

Ramadan nights, Eid and national day sales on the calendar

Retail trading patterns shift strongly during Ramadan, with late-night shopping and changed staffing, followed by a concentrated Eid peak in clothing, fragrance, sweets and gifts. Saudi National Day and Founding Day bring promotional periods, and city entertainment seasons can lift footfall in particular locations. Back-to-school matters for several categories.

Reorder points calculated from ordinary weeks will miss these peaks. I agree seasonal uplifts with your merchandisers and plan collection allocation to reach distant branches in time. Promotions for national days need to be configured and tested centrally so every till applies the same offer.

Workforce planning also intersects with the system. Retail is a sector where localization of the workforce receives particular attention, so HR and payroll requirements, staff roles in the POS and training material in Arabic should be part of the design. Check the current rules for your activities with your advisor.

I schedule remote workshops within the Sunday to Thursday week, and plan go-live for a calmer period, never the weeks before Eid. The Saudi Arabia hub describes how else I work with businesses in the Kingdom.