EDI and API Integrations - Fabric

Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.

fabric Dropship supports several integration options for suppliers, including direct system connections through API or EDI. These two methods provide the most flexible and automated data exchange for suppliers managing high volumes or using ERP/OMS systems.

• EDI Integration (Managed): Leverages standardized EDI documents exchanged using FTP or SFTP. While fabric manages the integration, suppliers must complete their own setup and testing. This option is ideal for suppliers already working with EDI systems or third-party EDI providers.
• API Integration: Connect your system to fabric Dropship using RESTful APIs for real-time data exchange. Best suited for suppliers with in-house technical teams or development resources.

You can initiate either integration during onboarding under the Transaction Integration task or after onboarding by contacting the fabric Dropship support team.

EDI Integration Overview

Electronic Data Interchange (EDI) automates transactions between your systems and fabric for specific document formats transmitted over FTP and SFTP. fabric hosts the FTP and SFTP servers and provides unique credentials for each supplier.

Integration process

1. Select EDI during onboarding for the Transaction Integration task, or later by submitting a support ticket.
2. Contact Dropship support to initiate setup. A member of the onboarding team will provide you with next steps and request the following information:
   • The EDI Qualifier: A short code that tells the receiving system the type of EDI ID being used.
   • The EDI ID: A unique identifier representing your business in EDI transactions, used to route messages between your system to fabric and vice versa.
3. fabric will provide unique FTP credentials along with testing instructions, including the EDI Qualifier and EDI ID for the specific merchant you are integrating with.
4. You must transmit test versions of all required EDI documents for validation.

Most suppliers choose to delay EDI integration until after onboarding, since it can involve additional costs and typically depends on having better visibility into expected order volume.

Supplier responsibilities

• Suppliers must manage their own EDI system or work with a third-party EDI provider.
• All outbound EDI documents must be submitted for review.
• If issues are found in formatting or content, suppliers must rework and re-submit the documents, which may delay onboarding.
• All EDI files are required to be placed into FTP/SFTP with the file extension EDI. Dropship won’t pull in any files that don’t have the EDI extension at the time they’re placed into the outbox.
• Files must not have any special characters such as an underscore (_) or ampersand (&). These file naming conventions won’t be recognized for processing.

Required EDI documents

API Integration Overview

fabric provides secure RESTful APIs for your team to build a fully automated connection to fabric Dropship. Integrating with APIs are ideal for suppliers with technical expertise or who already use internal systems like an ERP or OMS.

Integration process

1. Select API during onboarding for the Transaction Integration task, or later by submitting a support ticket.
2. Contact Dropship support to initiate setup. A member of the onboarding team will provide you with next steps.
3. Generate API credentials from the Settings menu.
4. fabric will provide:
   • API documentation
   • API keys
   • Brand ID
   • Test order details
5. Submit test transactions for validation, such as inventory syncs or shipment confirmations.
6. Once testing is approved, production credentials are issued and live transactions begin.

Supported API transaction types

How Data Sync Works