- On your own Shopify storefront you are the supplier of record. On Shopee, Lazada or TikTok Shop the obligation to issue the e-invoice rests with the platform operator instead [LHDN e-Invoice FAQ Q96 and Q100; Specific Guideline Section 14].
- Any single transaction exceeding RM10,000 must be issued as an individual e-invoice and cannot be consolidated. This applies to all businesses regardless of implementation phase, and it holds whether or not the buyer asks.
- Shopify’s standard checkout does not collect buyer Tax Identification Number (TIN) or Business Registration Number (BRN). Without those fields, business buyers are indistinguishable from consumers at the point of order.
- Consolidated e-invoices covering unclaimed business-to-consumer orders must reach LHDN within seven calendar days after month-end, using the general public TIN EI00000000010.
- Failure to issue carries RM200 to RM20,000 per invoice under Section 82C(1) of the Income Tax Act 1967, read with Paragraph 120(1)(d).
- The Shopify connector is available on the JomeInvoice Basic Plan and above. Integration access is not restricted to a premium tier.
Every order through your own Shopify storefront makes your company the supplier of record. That is the single fact that separates Shopify from your Shopee or Lazada channel, where the platform operator carries the issuance obligation instead of you. The obligation does not transfer, and it does not wait for reconciliation.
The practical problem is not whether to comply. It is that Shopify’s hosted checkout controls what buyer tax data you can collect, and LHDN’s routing rules depend on exactly that data. This guide sets out where the data constraint sits, how orders should be routed by buyer type and transaction value, and what to test before signing off on any integration.
Supplier of Record: Why Shopify Is Not Your Marketplace Channel
Businesses running both a marketplace presence and a direct storefront often assume a single compliance posture covers both. It does not, and the distinction is statutory rather than commercial.
For sales concluded on an e-commerce platform, LHDN places the obligation to issue the e-invoice or self-billed e-invoice on the platform provider, for all transactions conducted on that platform. Your Shopee and Lazada volume is therefore covered by the operator. Your Shopify storefront is not a platform in that sense: you are the seller, the merchant of record and the issuing party.
| Feature | Shopify Store | Shopee / Lazada / TikTok Shop |
|---|---|---|
| Who is the supplier? | You, the store owner | The marketplace operator |
| Who issues the e-invoice? | You, the Shopify store owner | The marketplace operator |
| Are individual sellers exempt? | No, you are the seller of record | Yes, the operator handles it |
| Integration required? | Yes, Shopify has no native MyInvois integration | No, the marketplace handles this |
The consequence is that marketplace volume and storefront volume need different treatments in the same compliance model. Our guide to e-invoicing on Shopee and Lazada covers the marketplace side; everything below concerns the channel you own.
The Hosted Checkout Constraint
Shopify’s advantage over a self-hosted stack is that the checkout is managed for you. That is also the constraint. You cannot freely add fields to a standard Shopify checkout, and the fields LHDN needs for individual e-invoice issuance are precisely the ones Shopify omits by default.
| Field LHDN requires | Standard Shopify checkout | Consequence if missing |
|---|---|---|
| Buyer TIN (business or individual) | Not collected | Order cannot be routed to individual issuance at point of sale |
| Business Registration Number (BRN) | Not collected | Business buyers indistinguishable from consumers |
| SST registration number | Not collected | Tax treatment must be inferred downstream |
| Itemised lines with tax classification codes | Available in the order payload | Usable, if the integration reads lines rather than order totals |
| Shipping and discounts as separate lines | Available in the order payload | Must not be netted into a single total |
Three routes exist for capturing the missing fields. Shopify Plus permits checkout customisation directly. Shopify B2B company accounts hold company-level attributes for invited buyers. On standard plans, a third-party app or a post-purchase capture step is required. Confirm which of the three your store is on before scoping any integration, because the answer determines whether buyer tax data arrives with the order or afterwards.
Where the data arrives late, the buyer-request flow becomes the primary capture mechanism rather than a fallback. That is a workable design, but it has to be a deliberate one.
Routing Shopify orders to LHDN by hand?
Integrate with SAP, Oracle, Dynamics 365 and more.
Local support from Malaysia.
Routing Orders Correctly
Once the data question is settled, routing is deterministic. Three rules decide where each order goes, and they apply in order of precedence.
- Value first. Any single transaction exceeding RM10,000 is issued individually. Consolidation is not available regardless of buyer type or buyer preference. The threshold applies per transaction, so ten separate RM1,200 orders from the same buyer in the same month do not aggregate into it.
- Buyer identification second. Orders carrying a valid buyer TIN and, for companies, a BRN are issued individually as business-to-business documents.
- Everything else consolidates. Remaining business-to-consumer orders enter the monthly consolidated pool, submitted within seven calendar days after month-end under the general public TIN EI00000000010.
One override sits across all three. A buyer who requests an individual e-invoice within the same calendar month as the transaction must receive one, and that transaction is removed from the consolidated pool. Our consolidated e-invoice guide covers the mechanics, and the RM10,000 rule explained covers the threshold in detail.
For a direct-to-consumer brand carrying premium price points, rule 1 is the one that bites. A furniture, jewellery or electronics catalogue produces threshold-crossing orders continuously, and each is an individual issuance obligation at transaction time.
Comparing the Integration Routes
Four routes, assessed on the criteria that matter at volume.
| Route | Handles buyer requests | RM10,000 routing | Maintenance burden | Best for |
|---|---|---|---|---|
| MyInvois portal, manual | Manual matching per request | Manual review per order | None, but linear staffing cost | Pilot channels and low volumes |
| Shopify app, invoice generation only | Usually not | Usually not | Vendor-side | Stores needing PDF documents, not LHDN submission |
| Custom API build | Whatever you build | Whatever you build | In-house, ongoing per LHDN revision | Teams with a standing integration platform |
| Compliance middleware | Automated matching and verification | Automatic exclusion from consolidation | Vendor-side | Storefronts outside the ERP transaction flow |
The second row is the one that catches buyers out. A substantial share of Shopify apps marketed around invoicing generate documents rather than submitting them to MyInvois for validation. A generated PDF is not a validated e-invoice, and the distinction is invisible until an audit. Ask any app vendor directly whether they submit to MyInvois and return a validation status, and whether they handle consolidation and adjustment documents.
We publish JomeInvoice through the Shopify App Store as well, so treat this as a category caution rather than a claim that apps are inferior to middleware. The question is capability coverage, not distribution channel. For a broader view see MyInvois versus e-invoicing software and the integration models guide.
How JomeInvoice Connects Shopify
JomeInvoice installs as a Shopify app and maps to a workspace in your JomeInvoice account. It is available on the Basic Plan and above rather than being gated to a premium tier, and it does not require a developer or a MyInvois portal login.
Orders sync automatically after installation and appear as draft invoices. Validation runs before submission: TIN format, tax classification codes, unit-of-measure values and line-item structure are checked, and errors surface for correction rather than returning as an Invalid status from LHDN afterwards.
Routing follows the three rules above without manual review. Invoices at or above MYR 10,000 are excluded from consolidation automatically and held for individual submission, a behaviour built into the consolidation logic rather than applied by a person checking order values.
Buyer requests are handled end to end. Each order receipt carries a Request e-Invoice link, the form pre-fills receipt number, date and amount from the original order, and submissions are verified against that order record. Approved requests convert the invoice from consolidated to non-consolidated, and the validated document reaches the buyer the following morning. Mismatches on receipt number, amount or date are rejected with a stated reason so the buyer can resubmit, and every request is tracked under Sales, Requests.
Post-validation adjustments run through Credit Notes, Debit Notes and Refund Notes, each linked to the original document by its LHDN reference. Cancellation is available within 72 hours of validation; beyond that, adjustment documents are the only route. See how to amend or cancel an e-invoice.
Multi-store groups run several storefronts under one workspace with separate settings and sequences per outlet, alongside physical retail if you operate it. JomeInvoice holds ISO 9001, ISO 20000-1 and ISO 27001 certification, is PDPA compliant and is MySTI certified (STI202501062).
What to Test Before Sign-Off
Five tests, each producing evidence you can put in front of an auditor.
- Place a threshold order. Submit an order above RM10,000 and confirm it is excluded from consolidation without anyone intervening.
- Place a composite order. Include a discount, a voucher and shipping. Confirm each arrives as a separate line with the correct tax classification code rather than netted into a total.
- Break a submission deliberately. Send a malformed TIN. Confirm the error is caught before MyInvois rather than returned as an Invalid status afterwards.
- Run the buyer-request path. Have a test buyer request an individual e-invoice, then confirm the transaction leaves the consolidated pool and the audit trail records the conversion.
- Reverse a validated order. Refund it and confirm a Refund Note is created, linked to the original LHDN reference, and submitted as a separate document.
Test 3 is the one that distinguishes a genuine compliance layer from a submission pipe, and test 5 is the one most often deferred until a real refund forces it.
Sources and Further Reading
- LHDN e-Invoice guidelines, the official guideline library including Specific Guideline v4.8
- LHDN e-Invoice frequently asked questions, covering the e-commerce platform provider obligation
- LHDN e-Invoice implementation timeline, phase dates by revenue band
- MyInvois portal, LHDN’s validation platform
- e-Invoicing for eCommerce in Malaysia
- LHDN e-invoice penalty structure
- Enterprise e-invoicing solutions
Disclaimer: This article is for general informational purposes only and does not constitute legal or tax advice. LHDN guidelines are subject to updates. Always refer to the latest official LHDN e-Invoice Guidelines at myinvois.hasil.gov.my and consult a qualified tax professional for advice specific to your business.
Last updated: 19 August 2026
Routing is the decision; the platform is not
Shopify’s hosted checkout determines when you learn who the buyer is, and that timing determines whether an order can be routed at the point of sale or only after the buyer comes back to you. Establish which Shopify tier you are on, decide whether buyer tax data is captured at checkout or through the request flow, then verify the RM10,000 exclusion and the validation-failure path against live orders. Those three answers, documented, are what a compliance review under the framework effective 15 December 2025 will ask you to evidence.
See your Shopify orders reach LHDN before you commit
Integrate with SAP, Oracle, Dynamics 365 and more.
Local support from Malaysia.
Disclaimer: This article is for general informational purposes only and does not constitute legal or tax advice. LHDN guidelines are subject to updates. Always refer to the latest official LHDN e-Invoice Guidelines at myinvois.hasil.gov.my and consult a qualified tax professional for advice specific to your business.
Frequently Asked Questions
Does Shopify support LHDN e-invoicing natively?
No. Shopify has no native MyInvois integration and its standard checkout does not collect buyer TIN or BRN. Malaysian sellers connect through a Shopify app that submits to MyInvois, a compliance middleware layer, a custom API build, or manual entry in the MyInvois portal.
Who issues the e-invoice for my Shopee and Lazada sales?
The platform operator. LHDN places the obligation to issue the e-invoice or self-billed e-invoice on the e-commerce platform provider for all transactions conducted on that platform. Your own Shopify storefront is different: there you are the supplier of record.
Can a Shopify order above RM10,000 be consolidated?
No. Any single transaction exceeding RM10,000 must be issued as an individual e-invoice. This applies to all businesses without exception, and it applies whether or not the buyer requests one.
Do we need Shopify Plus to capture buyer tax fields?
Not necessarily. Shopify Plus allows direct checkout customisation and B2B company accounts hold company-level attributes, but standard plans can capture the same data through a third-party app or through the post-purchase e-invoice request flow. Which route fits depends on whether you need the data at the point of order.
Which JomeInvoice plan includes the Shopify integration?
The Basic Plan and above. Integration access is not restricted to the Pro Plan. Confirm current plan details at [jomeinvoice.my/pricing](https://jomeinvoice.my/pricing/).
How do we correct a Shopify order after LHDN has validated the invoice?
Within 72 hours of validation the e-invoice can be cancelled. After that window, corrections require a Credit Note, Debit Note or Refund Note submitted as a separate document and linked to the original LHDN reference. Editing the Shopify order does not change the LHDN record.
Can one workspace cover several Shopify stores and physical outlets?
Yes. Multi-store and multi-brand operations run under a single JomeInvoice workspace with separate settings, sequences and tax configuration per outlet, covering storefront and physical retail together. Marketplace sales remain with the platform operator and do not route through it.
Last updated: 19 March 2026 | Written by Yinn Sheng Ng, Head of Marketing