Sage label printing: Sage X3, Sage 100/300 and Intacct
Print labels from Sage X3, Sage 100 and 300 and Sage Intacct — database views, export folders, 4GL/web-service triggers and the connector for cloud editions — with scenarios and a checklist.
Sage covers very different products under one brand: X3 for mid-market manufacturing and distribution, 100 and 300 for SMB accounting with inventory, Intacct in the cloud. What they share is a database or export your team can reach, which is enough for EtikStudio to print from any of them without custom development on day one.
Which integration paths fit each Sage product
| Product | Best path | How |
|---|---|---|
| Sage X3 | Embedded data (SQL) + REST / folder | Views on ITMMASTER, STOLOT and SDELIVERY; a 4GL entry point or web service call triggers the label, or an export drops a file. |
| Sage 100 / 300 | Embedded data (ODBC) + watched folder | ODBC to the item and lot tables; scheduled exports or a Visual Integrator job write CSV to a watched folder. |
| Sage Intacct | REST + connector | Smart Events or a platform script call the REST API through the connector at the warehouse. |
Typical scenarios
| Process | Label | Trigger |
|---|---|---|
| Receiving | Item and lot labels | Receipt posted |
| Production (X3) | Finished-goods labels with lot and expiry | Production tracking |
| Shipping | Delivery and SSCC labels | Delivery validated |
| Retail (100/300) | Price and shelf labels | Price update |
Recommended flow
Start with the database: expose read-only views and let the operator scan or select the record. Add the trigger when the process is stable — X3 web service or entry point, Visual Integrator export for 100, Smart Event for Intacct. The template does not change between steps.
Implementation checklist
- Identify the product and version; paths differ between X3, 100/300 and Intacct.
- Request read-only views with item, lot, expiry and customer fields.
- For Intacct, install the connector at each warehouse.
- Validate GS1-128 output before go-live.
How EtikStudio handles it
Whatever Sage product you run, the label is designed once, reads master data at print time and prints in the language of the printer on that site.
Integration details vary by ERP version, deployment and licensing. Adapters and worked examples are provided during implementation.