Custom Integration

  • Fillz can connect to an FTP server to deposit inventory files and retrieve orders.
  • FTP User IDs cannot contain symbols, such as: @ _ . 
  • Hostname must be valid (e.g.
  • Once you activate the Custom Marketplace in Fillz, our system will then begin to automatically check for order files.
  • Fillz does not support SFTP


Fillz can only export to a single directory. Choose The directory by adding it to the Hostname.

Example FTP Hostname:

If you do not specify a directory, inventory files will be deposited in the root directory. Once you activate the Custom Marketplace in Fillz, inventory updates will be automatically sent to this location.

Fillz can export inventory files in the following formats:

Amazon (.txt):

Deletes can be represented by a “d” in the “add/delete” column or by “0” in the quantity column.

BookHound (.tab)

FillZ Inventory Loader (.txt):

Deletes can be represented by a “d” in the “add/delete” column or by “0” in the quantity column.

Homebase 2.X (.txt)  
UIEE (.msg): Deletes are represented by any value greater than “1” in the XB| field or by “0” in CO| field.


You can expect the following types of export files from Fillz:

Purge Files
  • Filenames include the term purge when the file should be treated as a purge.
  • This file contains a seller’s entire active inventory. When the marketplace processes the file, it should remove all active inventory, and replace the seller’s existing inventory with the listings contained in the file.
  • Purges are initiated by the seller only. We’re unable to upload scheduled purge files in place of delta files.

Example filename: userid-yyyy-mm-dd-hh-mm-ss-full-purge.txt 

Delta Files
  • These are static naming conventions for Fillz and can’t be modified for Custom Marketplaces.
  • Fillz automatically sends delta files approximately every 30 minutes if there are changes/deletes to be exported.

Example add/modify filename: userid-yyyy-mm-dd-hh-mm-ss-part.txt

Example delete filename:  delete_userid-year-mm-dd-hh-mm-ss.txt 



  • Create an /orders directory on the server. Fillz will check it hourly for new files.
  • Order files must be in the Amazon Fulfillment Report format. If the headers and content of the file do not match the Amazon Fulfillment Report exactly, the order files won’t be retrieved by Fillz (see below for example order file).
  • The data in your file must be tab-separated, however the file must be have a .csv extension. This means you need to save your file in Tab Delimited Format, then change file extension from .txt to .csv.
  • When you are naming order files, they must follow this format or they won’t be picked up by Fillz: orders-yyyy-mm-dd-hh-mm-ss.csv (example: orders-2011-01-30-12-00-00.csv)
  • “payments-date” and “purchase-date” must be in this exact format or the file will not be picked up by our system: yyyy-mm-dd hh:mm:ss
  • Orders for Custom Markets must be processed directly on the Marketplace. At this time, Filz is unable to implement order confirmation for Custom Markets. If you have any questions, do not hesitate to contact us).
  • An example order file is attached to the bottom of this page.


We recommend that you use the NLST command to retrieve filenames, rather than the LIST command. The latter is non-standardized and can easily break if the listing format changes. Please see more information on this here.


For instructions on configuring and activating a Custom marketplace in Fillz, please click here.

For more information on Custom Marketplaces please click here.

Have more questions? Submit a request