ZATCA Phase 1 QR-Code Tax Invoice for Magento 2

核心功能

ZATCA Phase 1 compliant TLV (Tag-Length-Value) QR code, Base64-encoded, rendered on the invoice PDF and order email per the official spec

Encodes all five mandatory tags: seller name, VAT/TRN registration number, ISO-8601 invoice timestamp, invoice total with VAT, and the VAT total

Bilingual Arabic + English simplified tax invoice (Fatoorah) layout with correct RTL rendering for Arabic fields

Auto-injection into Magento's native invoice PDF via a plugin/interceptor on the renderer — no core overrides, no template fork you have to maintain

Observer on sales_order_invoice_save_after generates and persists the QR payload at invoice creation, so PDFs and emails stay consistent

Admin configuration under Stores → Configuration for VAT registration number, legal seller name and address, gated by a dedicated ACL resource

Built cleanly via di.xml dependency injection and a proper module.xml — survives bin/magento setup:upgrade and setup:di:compile

Works with Magento Open Source and Adobe Commerce 2.4.x; compatible with single-store and multi-store (per-website seller VAT details)

Compatible with the native Magento invoice email and standard PDF transactional documents

Optional integration test verifying the TLV byte structure and Base64 output against ZATCA validator expectations

Source delivered to you (no encryption, no license phone-home) so your team can audit and extend it

Installed by ECOSIRE on staging then production, with smoke-tested sample invoices before sign-off

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Magento 2 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

ZATCA Phase 1 (Fatoorah / Generation Phase) became mandatory for VAT-registered KSA merchants on 4 December 2021. Every tax invoice must carry a Base64-encoded TLV QR code plus the prescribed seller and VAT fields. Magento Open Source and Adobe Commerce ship no native ZATCA support — the stock Magento_Sales invoice PDF has no QR code and no Arabic layout. This module closes that gap.

ECOSIRE builds, installs and supports a focused module — installed under app/code/Ecosire/ZatcaPhase1 (or via your private Composer repo) — that hooks Magento's invoice generation without overriding core files. It uses a plugin (interceptor) on the PDF invoice renderer and an observer on sales_order_invoice_save_after to assemble the five mandatory TLV tags: seller name, VAT/TRN registration number, invoice timestamp (ISO-8601), invoice total (with VAT), and the VAT total. These are byte-packed into the Tag-Length-Value structure ZATCA mandates, Base64-encoded, and rendered as a QR code on both the native invoice PDF and the order/invoice email template.

The module adds a bilingual Arabic + English simplified tax invoice (Fatoorah) layout so the printed document reads correctly for KSA buyers and auditors. Seller details — legal name, VAT registration number, address — are configurable in the admin under Stores → Configuration, gated behind a dedicated ACL resource so only authorized roles can edit them.

This is an honest build-to-order engagement, not an instant Marketplace download. After purchase ECOSIRE confirms your Magento version (2.4.x), edition, theme and PDF stack, builds against it, and deploys to your staging then production environment. Pricing is a one-time USD 249 build; Phase 2 (e-invoicing integration / clearance) is a separate, larger scope you can grow into later.

你得到什么

A custom Magento 2 module (Ecosire_ZatcaPhase1) delivered as readable source under app/code or via a private Composer package

Installation and configuration on your Magento staging environment, then promotion to production after your sign-off

Admin setup of your seller legal name, VAT/TRN number and address, with the ACL role wiring

Sample ZATCA-compliant invoice PDF and email generated and validated against the Phase 1 TLV/QR spec

Short technical handover doc covering module structure, config paths, and how to adjust seller details

A bug-fix warranty window after go-live covering the delivered scope

Optional ongoing support/update retainer for Magento minor-version upgrades and any spec clarifications

这是给谁的

Small KSA merchant on Magento Open Source

A VAT-registered Saudi store owner who needs Phase 1 QR-code compliance now as a low-cost entry, without paying for a full Phase 2 e-invoicing integration yet.

Magento agency serving a Saudi client

An implementation partner who wants a clean, core-safe module they can audit and maintain, rather than hacking the stock invoice PDF template and breaking it on the next 2.4.x upgrade.

Finance / compliance lead at a KSA retailer

Responsible for ensuring printed and emailed tax invoices carry the correct TLV QR code and bilingual VAT fields so invoices pass ZATCA and auditor checks.

ZATCA Phase 1 QR-Code Tax Invoice for Magento 2 如何比较

标准	伊科西尔	定制建造	竞争对手	Magento 2 原生
ZATCA Phase 1 compliant TLV/Base64 QR code on invoices	包含	部分支持	包含	不包括在内
Bilingual Arabic + English (Fatoorah) invoice layout	包含	部分支持	部分支持	不包括在内
No core overrides (plugin/observer, upgrade-safe)	包含	部分支持	部分支持	包含
Built and tested against your exact Magento version/edition/theme	包含	包含	不包括在内	不包括在内
Installed and deployed for you (staging then production)	包含	部分支持	不包括在内	不包括在内
Readable, unencrypted source you can audit and extend	包含	包含	不包括在内	包含
Instant self-service download / activation	不包括在内	不包括在内	包含	包含
Direct ongoing support from the builder for this scope	包含	部分支持	部分支持	不包括在内
Phase 2 e-invoicing / clearance integration included	不包括在内	不包括在内	不包括在内	不包括在内

关于ZATCA Phase 1 QR-Code Tax Invoice for Magento 2的常见问题

How long until it's installed and working on my store? (delivery / lead time)

This is build-to-order, not an instant download. Typical lead time is 5–10 business days from when you confirm your Magento version (2.4.x), edition (Open Source or Adobe Commerce), theme and PDF stack, and provide staging access. ECOSIRE builds against your exact environment, deploys to staging for your review, then promotes to production after your sign-off. We give you a firm date once we've scoped your environment.

What do I get for the one-time USD 249, and is Phase 2 included?

The 249 covers the Phase 1 QR-code module build, installation on your staging and production environments, admin configuration of your seller/VAT details, a validated sample invoice, and a handover doc. Phase 2 (e-invoicing integration, XML/clearance with ZATCA's platform) is a separate, larger scope — this module is the deliberate low-cost Phase 1 entry point you can grow from.

How are updates and ongoing support handled?

The build includes a bug-fix warranty window after go-live covering the delivered scope. Beyond that, an optional support/update retainer covers Magento 2.4.x minor-version upgrades, theme changes that affect the invoice PDF, and any ZATCA spec clarifications. Because we deliver readable, unencrypted source, your own team can also maintain or extend it.

Will this break when I run setup:upgrade or upgrade Magento?

No core files are overridden. The module uses standard Magento 2 mechanisms — module.xml, di.xml dependency injection, a plugin/interceptor on the invoice PDF renderer, and an observer on sales_order_invoice_save_after. That means it survives bin/magento setup:upgrade and setup:di:compile and is far safer across 2.4.x upgrades than a forked invoice template.

Does it work on Adobe Commerce as well as Magento Open Source?

Yes. The module targets the shared Magento 2.4.x sales/invoice stack, so it works on both Magento Open Source and Adobe Commerce. We confirm your exact edition and version during scoping and build and test against it specifically, including multi-store setups where each website needs its own seller VAT details.

Can I configure my VAT number and seller details myself after delivery?

Yes. Seller legal name, VAT/TRN registration number and address are editable in the Magento admin under Stores → Configuration, protected by a dedicated ACL resource so only authorized admin roles can change them. We set your initial values during installation and show your team where to update them in the handover doc.