IT hears “ERP integration” and often asks for a standard API first. Integration can follow several paths: Excel or a staging table, LuckData, and HTTP API and submitting print jobs. You do not need a dedicated site per ERP brand.
Three common data paths
- Excel or a staging table: the business system exports or lands a sheet; LuckDesign binds columns to template variables. Good for a first go-live with few fields.
- LuckData: map business fields to label variables with less change to the ERP print program. Chanjet T+ is a standard example: LuckDesign owns design and local print; data comes from LuckData, Excel, or a staging table.
- LuckNext HTTP API and submitting print jobs: the system sends print jobs, many stations submit jobs, or you need multi-node. This is where you submit print jobs.
Enterprise also has the LuckDesign SDK to embed the designer and templates in a business UI—that is template design. LuckNext adds a print SDK and HTTP API. Do not mash the two SDKs into “one Enterprise SKU does everything.”
How to read SAP, Kingdee, Yonyou, Dynamics
SAP, Kingdee, Yonyou, Microsoft Dynamics, Chanjet, and similar use the same generic integration: document fields merge through a middle layer or API, then land on a template. The difference is which document the fields come from and whether you write back—not a dedicated site per ERP brand. Implementation is project-by-project.
Small inventory systems often start with Excel or a staging table. Groups, multi-plant, and systems that push print jobs then submit them through LuckNext. Vendor notes: ERP and business-system integration. T+ example: Chanjet T+ label printing.
Three questions at selection
Can data land on a sheet first? Must the business system push print jobs? How many printers and sites submit print jobs? If a sheet covers the first two, start with LuckDesign plus a data source. When the third appears, add LuckNext unified print.