ERP integration approach#
StackCube is designed to sit before ERP entry. It captures messy customer orders, creates reviewed order records, and then passes approved data downstream through the handoff path your team uses.
Integration levels#
| Level | Use when |
|---|---|
| Manual entry | You want review first and ERP volume is manageable |
| CSV handoff | ERP supports import templates and fields are stable |
| Supported ERP export | A supported provider such as Ecount is configured |
| Custom workflow | Multiple systems or approvals must be coordinated during onboarding |
Supported Providers#
The admin integration settings support Ecount ERP. SAP, Douzone, and Webhook providers may appear as preparing or disabled options and should not be treated as live guide paths unless enabled during onboarding.
Ecount Settings#
Ecount setup requires Open API credentials and export defaults.
| Field | Meaning |
|---|---|
| Environment | Production or sandbox |
| Export target | Sales order, sale, or purchases |
| Company code | Ecount company identifier |
| User ID | Ecount user with API access |
| API certificate key | Ecount Open API credential |
| Warehouse code | Required export value |
| Employee code | Optional person-in-charge mapping |
| Transaction type code | Company-specific ERP transaction type |
Warehouse code is required before saving or testing. Choose employee and transaction type codes according to your ERP operating policy.
Test and Run History#
After entering settings, run a connection test. Once saved, review run history after exports to track success, failure, and error messages.
If ERP export fails, first check customer code, item code, quantity, and warehouse code. Approval and ERP export can be considered separately, but repeated export failures usually mean catalog or customer master data needs correction.
Recommended rollout#
Start without deep ERP automation. Use StackCube to centralize intake and approval first. Once approved data is stable, automate the downstream handoff.
This prevents integration work from hiding basic catalog, pricing, and review issues.
Data mapping#
Map these fields before automation:
- Customer code
- SKU or ERP item code
- Quantity and unit
- Price and tax handling
- Delivery address
- Order memo
- External order identifier
If you plan to use Ecount export, align item and customer codes with ERP codes during setup. Missing codes may allow order approval but block ERP export.
When to use ERP export#
Use a supported ERP export when manual or CSV entry becomes the bottleneck after the review process is already stable.
Before starting provider setup or custom integration work, confirm that customer codes, item codes, tax handling, and export ownership are already stable in daily operations.