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

​
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.

​
How Clarus matches a file to its import

However a file arrives, Clarus has to work out which import configuration should process it. There are three ways to identify a file, and a configuration can use them in combination:

​
Matching on the contents of the file

Content matching reads a value from a named position inside the file and uses it to select the configuration. For EDI, that means addressing a segment and the element position within it — for example the message type held in the UNH segment, or the sender ID in the UNB segment. Where a configuration defines more than one criterion, all of them must match, so a file can be identified by message type and sender together.
This is what makes EDIFACT senders workable without bespoke development. EDIFACT files often arrive under an unpredictable filename, with every message type landing in the same folder — so neither the filename nor the folder can tell Clarus what the file is. Reading the message type out of the file itself can.
If no configuration matches an incoming file, the file fails rather than being processed by the wrong configuration. The log entry records the values that were read from the file, so you can compare them against the configuration and correct whichever is wrong. See Import errors.