> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.claruswms.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bespoke Imports

> When the standard SFTP import templates don't fit your source system, Clarus can build a bespoke import in TXT, CSV, XML, or EDI.

When the [standard import templates](/knowledgebase/integrations/use-sftp-for-imports) don't match the format your source system produces, Clarus can build a **bespoke import** tailored to it.

## Supported formats

| Format  | Notes                                                                                                  |
| ------- | ------------------------------------------------------------------------------------------------------ |
| **TXT** | Plain text, fixed-length or delimited                                                                  |
| **CSV** | Custom columns, headers, or structure                                                                  |
| **XML** | Custom schemas                                                                                         |
| **EDI** | Including 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

<Steps>
  <Step title="Share a sample file">
    Provide a sample of the file you need to send or receive.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Scope the build with your consultant">
    Your implementation consultant will confirm the mappings, logic, and delivery.
  </Step>
</Steps>

<Warning>Bespoke work is usually chargeable unless it was included in your original implementation scope.</Warning>