FullCircle Connector

Sync Orders, Fulfillments, Products, Purchase orders, Receipts, and Locations.

Pipe17 supports the following flows for Full Circle over FTP:

• Pull Orders from FullCircle
• Pull Products from FullCircle
• Push Fulfillments to FullCircle
• Push Receipts to FullCircle
• Pull Purchase Orders
• Pull Locations from FullCircle

Requirements

• Pipe17 Account
  Ensure you have a Pipe17 account. If not, book a demo with a Pipe17 representative.

• FullCircle
  Ensure you have access credentials (host, port, username, password) for your FTP server.

Connecting FullCircle to Pipe17

1. In your Pipe17 portal, navigate to Integrations > Add Integration.

2. Search for and select FullCircle Connector, then click Add.

3. The Connection Flow Settings page appears. You can configure settings now or later via the Integrations tab.

Required Connection Details

• Connection Protocol: Choose from FTP, FTPS, or SFTP.

• Host: Domain or IP of your FTP server (e.g., myftpserver.cloudhost.com).

• Port: Common ports include 21 (FTP), 22 (SFTP), 990 (FTPS).

• Username/Password: Credentials for your FTP account.

• Processing Action: Add a `.processing` to the end of the filename while the file is being processed.
• Post-processing Action: Remove the file, move it to a processed folder, or add `.processed` file extension.

• Whitelisted IPs: Your server must allow the following IPs:

  • develop: 54.244.107.167

  • stage: 52.32.223.95

  • master: 52.32.167.96

Click Save to complete setup.

Connection Flow Settings

Each entity has configurable directions and behaviors:

• Orders: Pull only
• Fulfillments: Push only
• Products: Pull only
• Purchase Orders: Pull only
• Receipts: Push only

• Locations: Pull only

Integration Specific Settings

Note: Although the FullCircle connector works over FTP the file format is not our standard FTP JSON or CSV. The files follow (EDI like) format specific to FullCircle.

Orders – Pull

Overview
Orders are pulled from FullCircle into Pipe17, including order numbers, line items, customer info, and shipping details. This enables centralized order tracking and management.

Settings
Specify the path where orders should be downloaded from: specify the file path on your FTP server where Pipe17 can fetch Orders from. You can also specify the file extension.

Exclude orders created before this date: By default, Pipe17 will begin pulling orders at the date/time of the integration becoming active. If you would like to modify this date/time, you can add an earlier or later date to this field. Otherwise, leave it blank.

Process only orders with matched numbers (regex): Only the Orders with matching ids will be processed, you can even specify a regular expression to match.

Sync Behavior
Orders sync on a schedule by polling FullCircle for new/updated files, which are then automatically imported.

Data Filtering and Rules

• Order Number Filtering: Only orders matching specific patterns (set in Order Filters) are imported.

• Location Mapping: Warehouse locations are matched to Pipe17 locations.

• Duplicate Handling: Existing orders in Pipe17 (based on external order ID) are skipped.

Additional Notes

• Files are marked as processed and moved post-sync as per default configuration.

• Retry logic handles errors.

• Result files summarize sync outcomes.

Fulfillments – Push

Overview
Pushes order fulfillment data from Pipe17 to FullCircle, including tracking info and shipment details.

Settings
Specify the path where fulfillments should be uploaded to: specify the folder path on your FTP server where Pipe17 can upload Fulfillments.

Select components for file name generation during upload: choose from a combination of Timestamp, Entity Id, Entity Type in generation of the uploaded filename.

Sync Behavior
Runs on a schedule to sync fulfillments which are created or updated in Pipe17.

Data Filtering and Rules
All fulfillment records are pushed without filters.

Additional Notes

• Requires order data to exist in FullCircle first.

• No sync limits or batching.

• Retry logic ensures successful delivery.

Products – Pull

Overview
Product catalog data is pulled from FullCircle into Pipe17, including product names, descriptions, pricing, and inventory.

Settings

• Product download path: specify the file path on your FTP server where Pipe17 can fetch Products from. You can also specify the file extension.

• Products SKUs Filter: Filters products by SKU patterns including strings & regular expressions; leave blank to import all.

Sync Behavior
Runs on a schedule. Only changed products since the last sync are imported.

Data Filtering and Rules
Invalid/incomplete product data is skipped and logged. Only filtered products (by SKU) are imported.

Additional Notes

• Large files are processed in batches.

• Failed files are retried.

• Duplicate prevention logic ensures clean data.

Purchases – Pull

Overview
Pulls customer purchase order data from FullCircle into Pipe17, including order numbers, line items, and warehouse info.

Settings

• Purchases In Path – specify the file path on your FTP server where Pipe17 can fetch Purchase Orders from. You can also specify the file extension.

• Purchases Status – Default status for imported orders can be set to 'draft', 'readyForFulfillment' or be left unset.

• Create arrivals if ingesting purchases - Create an Arrival (ASN) in Pipe17 when a Purchase Order is pulled.

Sync Behavior
Polling-based sync checks the FTP directory every few minutes and imports new files.

Data Filtering and Rules
Orders not matching the "Purchases Filter" patterns are skipped.

Additional Notes

• Process is automated.

• Errors trigger retry logic.

• No file size or quantity limits, but large files may affect performance.