- Five platforms have native JomeInvoice connectors: Shopify, WooCommerce, Loyverse, SalesPlay and Cloudbeds. All are available on the Basic Plan and above rather than being gated to a premium tier.
- Every other system, including SAP, Oracle, Microsoft Dynamics, NetSuite, Odoo and any custom or legacy platform, connects through CSV bulk upload, SFTP or the API. These are supported routes, not workarounds, but they are not pre-built connectors.
- What makes a platform e-invoice ready is buyer tax data capture and itemised line export, not feature count. A platform that exports order totals rather than lines forces manual correction before submission.
- Marketplace channels are covered by the operator. The obligation to issue the e-invoice for sales on an e-commerce platform rests with the platform provider [LHDN e-Invoice FAQ Q96 and Q100].
- Penalty enforcement is active for Phase 1, 2 and 3 companies. Their transition periods closed on 31 January 2025, 30 June 2025 and 31 December 2025 respectively [LHDN e-Invoice Specific Guideline v4.8, Table 16.1].
- Any single transaction exceeding RM10,000 must be issued individually and cannot be consolidated, on any channel and for all businesses regardless of implementation phase.
An enterprise does not choose an eCommerce platform. It inherits an estate: a direct-to-consumer storefront the brand team built, a point-of-sale system in the outlets, a booking system in hospitality, a marketplace presence, and a back-office system that was never designed to issue tax documents in real time.
So the useful question is not which platform is best in the abstract. It is which of your existing channels has a native path to LHDN MyInvois, which needs a file or API route, and which currently has no route at all. This article assesses the platforms with native integration, states the criteria that make any platform e-invoice ready, and sets out how to cover everything else.
The Two Criteria That Actually Decide Platform Readiness
Most platform comparisons rank on feature count. For e-invoice purposes only two properties matter, and both are about data rather than functionality.
Buyer tax data capture. LHDN requires the buyer TIN, or the company name, TIN and BRN for business buyers, before an order can be issued as an individual e-invoice. Platforms that store these at order level give you a direct routing path. Platforms that do not push every transaction into the consolidated pool by default, which is legitimate for consumer sales and wrong for a business buyer who requested a formal document.
Itemised line export. LHDN requires individual line items, unit prices, quantities and tax classification codes per item. Shipping fees, vouchers and discounts count as separate lines. A platform that flattens an order into a single payable amount forces a correction step before every submission, which is where enterprise estates accumulate silent errors.
Everything else, including theme flexibility, app ecosystem and hosting model, is a commercial decision with no compliance consequence.
Platforms With Native JomeInvoice Integration
Five platforms connect directly. Orders sync without an export step, and the same validation and submission layer applies to all of them.
| Platform | Channel type | Best for | Known constraint |
|---|---|---|---|
| Shopify | Hosted storefront | Direct-to-consumer brand arms and multi-store groups | Standard checkout does not collect TIN or BRN; needs Shopify Plus, B2B company accounts, or the buyer-request flow |
| WooCommerce | Self-hosted storefront | Enterprises wanting full checkout control over buyer tax fields | Plugin and hosting maintenance sits with your team; custom checkouts may need CSV mapping |
| Loyverse | Point of sale | Multi-outlet retail with a storefront alongside | POS-originated data; storefront still needs its own path |
| SalesPlay | Point of sale | Retail and F&B chains running counter transactions | As above |
| Cloudbeds | Hospitality property management | Hotel and resort groups issuing folio-based documents | Reservation-driven billing differs from order-driven retail |
Shopify
Shopify installs as an app and maps to a workspace. Orders sync automatically and validation runs before submission. The constraint is the hosted checkout: buyer tax fields are not collected on standard plans, so either you customise through Shopify Plus, use B2B company accounts, or rely on the post-purchase request flow. Our enterprise Shopify routing guide covers the routing rules in detail.
WooCommerce
WooCommerce connects through the Integration Module, with orders syncing when marked Completed. Because it is self-hosted, you can add TIN, BRN and SST registration fields to the checkout with a field editor plugin or a code change, which makes it the stronger option where business buyers are a meaningful share of storefront volume. The trade-off is that plugin and hosting maintenance is yours. See the WooCommerce enterprise assessment.
Loyverse and SalesPlay
Both are point-of-sale systems rather than storefronts, and both matter to enterprises running physical outlets alongside an online channel. Counter transactions and online orders feed the same compliance view, so consolidation and buyer requests behave identically across both streams rather than requiring two processes. For the wider retail picture see our POS e-invoice middleware guide and the comparison of ePOS versus POS integration for retail.
Cloudbeds
Cloudbeds covers hospitality groups where billing originates from reservations rather than orders. Sales documents and credit notes raised in Cloudbeds sync into the same workspace and follow the same submission and consolidation path.
Not sure which of your channels reach LHDN?
Integrate with SAP, Oracle, Dynamics 365 and more.
Local support from Malaysia.
Everything Else: File and API Routes
No enterprise estate consists only of the five platforms above. The remaining channels connect through three supported routes, and it is worth being precise about what they are.
| Route | How it works | Best for | Risk if ignored |
|---|---|---|---|
| CSV bulk upload | Export orders, map columns once, upload | Legacy systems and low-frequency channels | Manual cadence; someone must own the upload schedule |
| SFTP | Scheduled file transfer without manual upload | Higher-volume channels needing unattended transfer | File-format drift if the source system changes |
| API | Direct programmatic submission | Enterprises with a standing integration platform | Requires developer capacity to build and maintain |
These are not second-class paths. Field mapping is configured once and applied to every subsequent upload, and SFTP, direct upload and API submissions all use the same standardised field structure and the same validation layer as native connectors.
This is also how ERP and accounting systems connect. JomeInvoice does not ship pre-built connectors for SAP, Oracle, Microsoft Dynamics, NetSuite, Odoo, Sage or Xero. Those systems, and any custom or legacy POS, integrate through the API, CSV upload or SFTP. If a vendor tells you they have a plug-and-play connector for a major ERP, ask to see it working against your instance before believing it. Our integration models guide sets out the architectural options.
QuickBooks is the one accounting system with a direct JomeInvoice path, through a field-mapped upload flow rather than a real-time connector.
Marketplace Channels Are Already Covered
Sales concluded on Shopee, Lazada or TikTok Shop do not need a route, because the obligation to issue the e-invoice or self-billed e-invoice rests with the e-commerce platform provider for all transactions conducted on that platform.
The practical implication for an enterprise estate is that marketplace volume should be explicitly excluded from your own submission scope, and that exclusion should be documented. Estates that fail here usually fail by double-counting rather than by omission. Our guide to e-invoicing on Shopee and Lazada covers the split.
Matching Channels to Routes
Use this to map your estate rather than to pick a platform.
| Your situation | Recommended route | Why |
|---|---|---|
| DTC storefront on Shopify, consumer-heavy | Native connector, buyer-request flow as capture mechanism | Consolidation carries most volume; requests handle the exceptions |
| Storefront with significant B2B volume | WooCommerce with checkout tax fields added | Buyer data captured at order time routes to individual issuance without a follow-up step |
| Multi-outlet retail plus online | Native POS connector plus storefront connector, one workspace | Single compliance view across both streams |
| Hospitality group | Cloudbeds connector | Reservation-driven billing handled natively |
| ERP-issued B2B invoicing already live | Keep the ERP module | Do not add a layer to a channel that already issues at transaction time |
| Legacy or custom channel | CSV, SFTP or API | Same validation layer, no platform replacement |
| Marketplace sales | No route needed | Platform operator carries the obligation |
The fifth row is the one enterprises most often get wrong in the other direction, by adding middleware to a channel the ERP already covers properly. Route selection should follow where the data already lives.
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
- MyInvois integration explained
- Consolidated e-invoice rules
- e-Invoicing for eCommerce Malaysia: the operational workflow
- 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
Coverage is the deliverable, not platform choice
Nothing here argues for replacing a platform. The output you want is a documented map of every revenue channel, the route each one takes to MyInvois, and the party responsible for it. Channels with a native connector are straightforward. Channels on CSV, SFTP or API need a named owner and a cadence. Marketplace channels need an explicit exclusion. A compliance review under the framework effective 15 December 2025 can cover up to two assessment years, so the map needs to hold for periods already closed as well as the current one. Once the map exists, the remaining work is operational: order sync, buyer request handling and monthly consolidation. Our e-invoicing workflow guide for online stores covers that day-to-day layer in detail.
Map your channels before your next compliance review
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
Which eCommerce platforms integrate natively with JomeInvoice?
Five: Shopify and WooCommerce for online storefronts, Loyverse and SalesPlay for point of sale, and Cloudbeds for hospitality. All are available on the Basic Plan and above. Every other system connects through CSV upload, SFTP or the API.
Do we need to replace our eCommerce platform to comply?
No. JomeInvoice operates as a compliance layer between your existing systems and LHDN MyInvois. Platforms without a native connector are covered by CSV upload, SFTP or API submission, which use the same validation and field structure as native connectors.
Is there a pre-built connector for SAP, Oracle or Microsoft Dynamics?
No. Those systems, along with NetSuite, Odoo, Sage and Xero, connect through the API, CSV bulk upload or SFTP rather than a pre-built connector. Treat any claim to the contrary as something to verify against your own instance.
What makes an eCommerce platform e-invoice ready?
Two properties. It must capture buyer tax identification at order level, meaning TIN for individuals and company name, TIN and BRN for businesses. It must also export itemised line data with unit prices, quantities and tax classification codes, with shipping and vouchers as separate lines rather than netted into a total.
Do we issue e-invoices for our Shopee and Lazada sales?
No. The obligation rests with the e-commerce platform provider for all transactions conducted on that platform. Exclude marketplace volume from your own submission scope and document that exclusion, because double-counting is the more common error.
Can one workspace cover storefronts, outlets and a hotel property together?
Yes. Multi-brand and multi-channel operations run under a single workspace with separate settings, sequences and tax configuration per outlet, so storefront, point-of-sale and property-management channels share one compliance view.
Does the RM10,000 rule apply differently by channel?
No. Any single transaction exceeding RM10,000 must be issued as an individual e-invoice and cannot be consolidated, whichever channel it originates from. This applies to all businesses regardless of implementation phase.
Last updated: 19 August 2026 | Written by Yinn Sheng Ng, Head of Marketing