Custom Field Mapping

Handle partner-specific fields without breaking your standard workflow.

Not every partner sticks to the basics. Some require extra references, codes, qualifiers, or custom data points that don’t exist in your standard document layout.

Custom Field Mapping lets you capture, map and deliver those fields cleanly — without rebuilding your integration every time a partner has a slightly different requirement.

The problem it solves

Custom fields create friction when they’re managed ad-hoc:

• partners require extra references (department codes, location IDs, project refs)

• custom qualifiers differ by retailer or channel

• fields get “stuffed” into notes or unused segments

• changes lead to rejects because mappings aren’t consistent

• teams end up maintaining one-off logic per partner

Custom Field Mapping keeps variation controlled and scalable.

What Custom Field Mapping does

Map additional fields per trading partner

Capture and map extra partner-required data points without impacting your baseline document structure.

Transform and validate custom fields

Apply rules like formatting, default values, conditional logic, and code lookups so fields are always delivered in the expected structure.

Keep standard flows stable

Custom requirements don’t force you to redesign your entire flow — you extend what’s needed while keeping the rest consistent.

Maintain traceability

Mapped custom fields remain part of the document trail for troubleshooting, auditing and partner queries.

How it works

1) Identify the custom requirement
Define the additional field(s) required for a partner or internal process.

2) Map from your source data
Pull values from your ERP/WMS/export, or add controlled defaults where needed.

3) Apply mapping rules
Transform and validate the custom fields so they meet partner expectations.

4) Deliver and monitor
Send documents as normal, with custom fields included, tracked and supported.

Key benefits

• Fewer rejects: meet partner requirements accurately

• Less rework: avoid one-off “special case” handling

• Faster onboarding: handle variations without slowing projects

• Cleaner governance: custom fields are controlled and traceable

• Scales across partners: add new requirements without messy builds

Best-fit use cases

• Retailers requiring additional references or qualifiers

• Multi-channel operations with differing data needs

• Suppliers handling department codes, cost centres or project refs

• Businesses needing partner-specific routing or labelling fields

• Teams expanding into new regions with different standards

FAQ

How is this different from Field Level Mapping?
Field Level Mapping covers the full document structure. Custom Field Mapping focuses on adding and managing extra partner-specific fields without disrupting your standard workflow.

Can custom fields be different per partner?
Yes — custom requirements are often partner-specific, and the mapping can reflect that cleanly.

Can we validate custom fields before sending?
Yes — validations and rules can be applied so documents don’t fail after delivery.

Does this remain traceable for audits and support?
Yes — custom fields are part of the document trail, making troubleshooting and partner queries easier.