Partner templates
A partner template is a pre-built field mapping for a widely used external system. Picking a template when you create a partner gives you a working mapping in one click.
Templates ship with the platform and are maintained by the Datamingle team. You can customize a template after applying it — you're not locked to the shipped version.
Available templates
Template availability grows over time. The shipped set covers the systems we see most often in the field:
| System | Resources covered |
|---|---|
| Acumatica | Orders, Inventory, Products, Locations |
| SAP Business One | Orders, Inventory, Products |
| NetSuite | Orders, Products |
| Shopify | Orders, Products, Inventory |
| Logo ERP | Orders, Products |
| Mikro ERP | Orders, Products |
| Custom | Empty mapping (start from scratch) |
Check the dashboard for the current list — templates are added regularly without a platform release.
What a template contains
Each template defines, per resource type:
- Field map — source → target field renames, including dot paths.
- Nested mappings — array-to-array transforms (order lines, inventory rows).
- Static values — metadata tags injected into every request (e.g.
metadata.source = "acumatica"). - Identifier field — which field resolves
{identifier}in URLs.
See Field mapping for the full capability set.
Applying a template
- Settings → Integrations → Partners → New partner.
- Select the template.
- Review the suggested mapping for each resource. Adjust field names if your system is customized.
- Save.
When none of the templates fit
Create a Custom partner. The first payload you send — with no mapping yet — must use internal field names. Build the mapping incrementally in Settings → Integrations → Partners → {partner} → Field mapping.
Request a template
If you need a template we don't ship, contact support with a sample payload. We add templates in the background — no platform release needed.