1. Pipe17 Help Center
  2. Connectors
  3. Full Circle

Connect FullCircle to Pipe17

Pipe17 Support Manager

The FullCircle connector exchanges files with the Full Circle ERP over FTP, FTPS or SFTP. Full Circle drops orders, purchase orders and products as files on an FTP server, the app imports them, and the app writes fulfillment and receipt files back for Full Circle to pick up.

The files use Full Circle's own EDI-like warehouse format, not the standard Pipe17 FTP JSON or CSV format. Each file type has its own extension: .940 orders, .943 purchase orders, .832 products, .945 fulfillments and .944 receipts.

Which Full Circle tile to pick: The catalog has two Full Circle connectors that move data in opposite directions.

  • FullCircle (this article): Full Circle sends orders out to be fulfilled, and the app returns fulfillments and receipts in Full Circle's warehouse file format (.940, .945).
  • Full Circle (Circlify): the app sends orders, shipping requests and returns from your other channels into Full Circle, and pulls products, inventory, fulfillments and return receipts from Full Circle as tab-delimited text files. See Connect Full Circle (Circlify) to Pipe17.

If you aren't sure which file format your Full Circle setup uses, ask your Full Circle contact or contact Pipe17 support before you connect.

Setup

Before you begin

  • An FTP, FTPS or SFTP account that both Full Circle and Pipe17 use: host, port, username and password.
  • The user needs read, write, rename and delete permissions on every folder the integration uses.
  • If the server only accepts known IP addresses, allow the Pipe17 IP addresses. See Whitelisted IPs for Connectors.
  • The folders where Full Circle drops and picks up files. The defaults are /orders-in, /purchases-in, /products-in, /fulfillments-out and /receipts-out.
  • The Full Circle warehouse IDs that appear in your order files, to set up locations.

Get your FTP credentials for Full Circle

  1. Ask your Full Circle contact, or whoever hosts the FTP server, for the host name, protocol (FTP, FTPS or SFTP), port, username and password. Ask for FTPS or SFTP if the server supports it.
  2. Agree on the folder for each file type and which side writes to it. Full Circle writes .940, .943 and .832 files. The app writes .945 and .944 files.
  3. Ask for the warehouse ID Full Circle uses for each warehouse in the order files.
  4. Test the login with any FTP client. Create a folder, upload a file, download it, rename it and delete it to make sure all permissions are set.

Connect in the app

  1. Navigate to Integrations and click Add integration.
  2. Search for FullCircle and select it. The Connect FullCircle pop-up opens.

Note: Leave every flow except Pull locations off on the integration's Settings tab until you confirm the connection.

Connect FullCircle pop-up (top)
Connect FullCircle pop-up (bottom)
  1. In Connection protocol, select FTP, FTPS or SFTP. FTP is selected by default. FTPS or SFTP is recommended.
  2. Leave Disable TLS validation off. Turn it on only to test an FTPS server whose certificate can't be validated.
  3. In Host, enter the host name without the protocol, for example ftp.example.com. Don't include ftp://.
  4. In Port, enter the port. It's prefilled with 22. Use 21 for FTP and 22 for SFTP. For FTPS on port 990, the app switches to port 21.
  5. Enter the Username and Password.
  6. In Pick operation to be made while processing inbound file, select No action required (default) or Add '.processing' extension (rename).
  7. In Pick operation to be made after processing inbound file, select what happens to an imported file: No action required (default), Add '.processed' extension (rename), Move to ./processed folder or Remove file. To move files, the processed folder must exist and the user must be able to write to it.
  8. Optional: turn on Check FTP write permissions before processing to check write access to the folders before each run.
  9. Optional: turn on Upload results for incoming files. For each imported file, the app uploads a file with the .results extension that lists the result for each record.
  10. In Delete old files after, select Never delete (default) or a number of days from 7 to 90. The app then deletes older files from the configured folders, including result files and the processed folder.
  11. Click Connect. The app connects to the server.

Note: If you don't have the credentials yet, click Add without credentials. The integration is added but doesn't sync until you enter the credentials on the Connection Details tab and click Save.

Confirm the connection

  1. On Integrations, check that the FullCircle integration shows Connected and that its switch is on. If it shows Error, check the protocol, host, port, username and password on the Connection Details tab. If it shows Not Configured, enter the credentials and click Save.
  2. In the integration settings, enter your Full Circle warehouses in Location names as id:name, for example 01:Main Warehouse, and click Save. Within about 5 minutes, go to Inventory > Locations and check that the locations appear.
  3. Ask Full Circle to drop one test order file in the orders folder, or pick one order number from a file that's already there.
  4. Add the order number to Process only orders with matched numbers (regex). Turn on Pull orders and click Save.
  5. Wait about 5 minutes. The app checks the folders every 5 minutes. Check that the order appears in Orders at the right location. If you turned on Upload results for incoming files, the .results file shows whether each order was imported or skipped.
  6. To test fulfillments, turn on Push fulfillments to FullCircle and click Save. After the test order is fulfilled, check that a .945 file appears in the fulfillments folder within a few minutes.
  7. Clear Process only orders with matched numbers (regex) and click Save. Then turn on the other flows you need.

Supported flows

  • Pull locations (from the Location names setting)
  • Pull orders from Full Circle (.940 files)
  • Pull products from Full Circle (.832 files)
  • Pull purchase orders from Full Circle (.943 files)
  • Push fulfillments to Full Circle (.945 files)
  • Push receipts to Full Circle (.944 files)

Settings

Only Pull locations is on when you add the integration. Turn on each flow you need in the integration settings and click Save. Each inbound flow picks up new files from its folder every 5 minutes. Files with the reserved extensions .processing and .processed are never imported, even if you name them in a path.

Locations

Pull locations Creates a location for each entry in Location names. Default: on.
Location names Your Full Circle warehouses as id:name, for example 01:Warehouse A. The ID must match the warehouse value in the order files, so imported orders get the right location. Default: one location, fc-default:Full Circle. If you clear the list, the app creates one location named after the integration.

Products

Pull products Imports products from .832 files. Default: off.
Specify the path where products should be downloaded from Folder and file mask for product files. Default: /products-in/*.832.
Process only products with matched SKUs (regex) Imports only SKUs that match one of the values or regular expressions. Leave empty to import all.

Orders

Pull orders Imports orders from .940 files, with line items, customer and shipping details. Default: off.
Specify the path where orders should be downloaded from Folder and file mask for order files. Default: /orders-in/*.940.
Exclude orders created before this date If empty, the integration creation date is used. Set an earlier or later date to change it.
Process only orders with matched numbers (regex) Imports only order numbers that match one of the values or regular expressions. Use it for testing, then clear it. Skipped orders are listed as skip.filter in the results file.

Fulfillments

Push fulfillments to FullCircle Writes a .945 file for fulfillments created or updated in the app, including tracking information. Default: off.
Specify the path where fulfillments should be uploaded to Default: /fulfillments-out.
Select components for file name generation during upload Builds the file name from any of Timestamp, Entity Id and Entity Type. Default: Entity Type and Timestamp.
Wait until the entire order is fulfilled, then send fulfillment information at once Holds fulfillments until the order is Fulfilled, then sends all of the order's fulfillments together, once. Default: off.

Purchase orders

Pull purchase orders Imports purchase orders from .943 files, with line items and warehouse. Default: off.
Specify the path where purchase orders should be downloaded from Default: /purchases-in/*.943.
Status to be set for a new purchase 'Draft' (default), 'Ready for fulfillment' or Not set.
Create arrivals if ingesting purchases Also creates an arrival (expected inbound shipment) for each imported purchase order. Default: off.

Receipts

Push receipts to FullCircle Writes a .944 file for receipts created or updated in the app, so Full Circle has a record of what was received. Receipts are sent about 10 minutes after their last update. Changes made in Full Circle don't come back to the app. Default: off.
Specify the path where receipts should be uploaded to Default: /receipts-out.
Select components for file name generation during upload Builds the file name from any of Timestamp, Entity Id and Entity Type. Default: Entity Type and Timestamp.

Import specific files again

The integration has three actions that import named files on demand: Pull orders from a file, Pull products from a file and Pull purchases from a file. Use them to re-import a file that failed or was skipped.

Troubleshooting

  • The integration shows Error after you click Connect.
    The app couldn't log in. Check the protocol, host (without ftp://), port, username and password, and that the server allows the Pipe17 IP addresses. If the connection keeps failing for about 6 hours, the app turns the integration off. Fix the credentials and turn it back on.
  • Orders aren't imported.
    Check that Pull orders is on, that the files are in the orders folder with the .940 extension, and that Process only orders with matched numbers (regex) is empty or matches the order number. Files ending in .processing or .processed are ignored. Turn on Upload results for incoming files to see why each order was skipped.
  • Imported orders have no location or the wrong one.
    The warehouse ID in the order file must match an ID in Location names. Add the missing id:name entry and click Save.
  • Files aren't renamed, moved or deleted after import.
    The FTP user needs write, rename and delete permissions on the folder. For Move to ./processed folder, the processed folder must exist. Turn on Check FTP write permissions before processing to catch permission problems early.
  • No .945 file for a fulfilled order.
    Check that Push fulfillments to FullCircle is on. If Wait until the entire order is fulfilled, then send fulfillment information at once is on, nothing is sent until the whole order is Fulfilled.
  • The FTP server fills up with old files.
    Set Delete old files after on the Connection Details tab.

Need Help?

If you need additional assistance:

  • Use Ask Pippen, our AI agent, located at the top of the platform page.
  • Submit a support request with as much relevant detail as possible. Learn how to submit a request.

We’re here to help you succeed with your operations.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.

Have more questions?
Submit a request
Share it, if you like it.