Skip to main content
When the standard import templates don’t match the format your source system produces, Clarus can build a bespoke import tailored to it.

Supported formats

FormatNotes
TXTPlain text, fixed-length or delimited
CSVCustom columns, headers, or structure
XMLCustom schemas
EDIIncluding EDIFACT message types such as DESADV, IFTMIN, RECADV, ORDERS, and ORDRSP

What a bespoke interface includes

Bespoke interfaces are scoped against your actual file samples and field mappings. They typically include:
  • Validation rules
  • Conditional logic — for example, routing serial-tracked items differently to bulk items
  • Any required acknowledgement files

Getting started

1

Share a sample file

Provide a sample of the file you need to send or receive.
2

Write a short brief

Describe the source or destination system and what the interface needs to do, so the integration team can size the work.
3

Scope the build with your consultant

Your implementation consultant will confirm the mappings, logic, and delivery.
Bespoke work is usually chargeable unless it was included in your original implementation scope.