Commerce7 Integration


Commerce7 – FORT integration

Orders originating in Commerce7 can be synched with FORT.

To connect to a Commerce7 account:

  1. make sure a "Remote Upload Key" is entered on the company page. It can be found in the "Integrations(s)" section.
  2. create and associate a FORT client user with the Commerce7 account (the "Login" field) - It will be set as the user for the account's order upload data within FORT.
  3. set fields Default Service Level, Check Address, and Send Transaction Email. These values will be used when importing orders.

There are 2 ways that a company or marketing code can be connected to a Commerce7 account:

1) Connection Type "Integration": A Warehouse Portal Admin will need to enter a Commerce7 username/password and tenant (The tenant name is case sensitive). (ex:  We recommend creating a new username for the API login such as This information can be entered on the company page in the "Integrations(s)" section, or (if you want the Commerce7 account associated with a Marketing Code) in the Marketing Companies section.


2) Connection Type "App": For this connection type, go to the App store within Commerce7 and search for "FORT Systems" or “FORT Ship”, and click to Install (make sure to install only 1 of the apps, not both).

Two fields will display: "FORT Company Code" (required) and "FORT Marketing Code". Enter the "Company Code" of the company you are trying to connect to (The code can be found in the Company Profile section on the company page.) The "FORT Marketing Code" field is not required - Enter a code if you are trying to connect your account for each Marketing Company. Note that FORT Marketing Codes are only 2 characters, so only the first 2 characters entered in Commerce7 will be considered. (e.g., if you enter "CODE", only "CO" will be used.) FORT will search to see if the company found with the "FORT Company Code" has a Marketing Code that matches the entered code.

If no Marketing Company exists for that Code, a Marketing Company will be created. The Commerce7 account/tenant will be setup for the Company/Marketing Code you entered.


The "Remote Upload Key" should be entered automatically, and a FORT client user should be created automatically.

When connecting FORT with a Commerce7 account through the app, you shouldn't need to make any changes on the company page.

You can still update the following optional setting fields if desired: Default Service Level, Order Delivery Method, Check Address, RSD Required, Flag Errors, and Send Transaction Email.

  • Default Service Level: This setting is essentially a backup that is used for a package's service level if the shipping code found in Commerce7 does not match a FORT service level code.

    All of the FORT service level codes can be found here:

    To set the code in Commerce7, go to Settings -> Shipping, and then click on the appropriate Shipping Zone. The Shipping Services for that zone will then be listed. 

    Edit the appropriate Shipping Service and change the value for “Code” to match the desired service level code in FORT:

  • Order Delivery Method: The options for this field are “Ship” and “Pickup”, with “Ship” being the default. FORT will only look for Commerce7 orders that have an Order Delivery Method found in the set list on FORT. If Pickup orders are set to upload into FORT, the Pick Up address will be set for the Recipient Address, and the service level will be set to WCP.
  • Check Address: The setting whether to check recipient address when uploading into FORT. If turned off, FORT will assume all addresses have been verified.
  • RSD Required: If set to “Yes”, will only upload Commerce7 orders that have a Requested Ship Date set. When determining the RSD, FORT will first look to see if a Requested Ship Date was set at Order creation within Commerce7. If no Requested Ship Date was set (or if you’d like to overwrite the Commerce7 Requested Ship Date) you can add an RSD tag. FORT will look for a tag with the format “RSD:yyyy-mm-dd”. 
  • Flag Errors: If this setting is turned on, orders that fail to upload into FORT will be flagged within Commerce7. This will make the orders with errors more obvious within Commerce7. The flags are also beneficial because FORT will ignore orders with FORT Error flags for 24 hours (this will prevent the orders from failing to upload over and over with the same errors). These flags will say “FORT Error mm/dd/yyyy hh:mm:ss”. Once the order has been successfully uploaded, the flag will be removed. If you know you have fixed the underlying issue, you could also manually remove the flag so the order will attempt to upload again the next time the scheduled task is run.
    To manually remove the flag, click the pencil next to flag in Commerce7. Then click on "More Actions"->"Delete"
  • Send Transaction Email: The setting to determine whether to send Commerce7 emails at Fulfillment.

You can use Commerce7 tags to add information to the FORT order. For example, if no Requested Ship Date was set in Commerce7 (or if you’d like to overwrite the Commerce7 Requested Ship Date) you can add an RSD tag. FORT will look for a tag with the format “RSD:yyyy-mm-dd”. 
Similarly, you can add tags to set FORT upload data for Special Instructions, Delivery Instructions, and Gift Message. For example, if the tag “SI:Ice Pack” were added in Commerce7, “Ice Pack” would get set as the Special Instructions in the FORT order.

FORT will look for SI -> Special Instructions, DI -> Delivery Instructions, and GM -> Gift Message.
You can set Gift Message/Delivery Instructions at order creation in Commerce7 (there is a Gift Message field, and the Shipping Instructions field → Delivery Instructions in FORT). If those messages are found in addition to tags, the messages will be concatenated. For example, if Commerce7 has “Shipping Instructions” set to “Main Message”, and the tag “DI:Tag Message”, in FORT the delivery message would be set to “Main Message; Tag Message”.

C7 Tag functionality described here:

If you uninstall the app in Commerce7, the setup FORT/Commerce7 connections associated with your tenant will be turned off.

A scheduled task will run every 30 minutes to attempt to upload Commerce7 Orders that are Not Fulfilled or Partially Fulfilled (not in process at the FORT warehouse), and have been updated/created since the last successful upload. The system will check every morning on any previously unsuccessfully uploaded orders and will attempt to reupload them. If you don’t want to wait for the system to check orders, you can click on the update button to check for orders right away.

“Quarantined” orders are prevented from being Uploaded to FORT. Once such orders are no longer set to "Quarantined", they will attempt to be uploaded the next time the scheduled task runs. 

The system will stop trying to upload failed Commerce7 orders if they have not been updated in Commerce7 for over 30 days.

"In House” orders are prevented from being Uploaded to FORT. To create In House orders, use the C7 Tag functionality described here:

Commerce7's "channels" map to FORT Order types as follows:

C7 Channel >> Type - Subtype

Web >> Web

Club >> Club

Inbound >> Other - Inbound

Other >> Other

Marketplace >> Other - Marketplace


Use the Commerce7 Transaction Email-Yes/No” in the Orders Integration C7 section of the company page to set whether or not the Commerce7 Transaction email is sent. The default is “Yes”.

FORT uses the C7 Customer email for the FORT Ship-To email because C7 does not provide separate Bill-To and Ship-To email addresses.

If the service level designated in C7 can’t be found in our system, FORT will use the Default Service Level set on the company page.

When the scheduled task runs, it looks for packages that are printed, and a “Fulfillment” will be added to the Commerce7 order. (A “Fulfillment” is a package status update.)  There will be one “Fulfillment” for each package generated in Fort Systems, so if FORT splits an order into 3 packages, then there will be 3 separate “Fulfillment” records in Commerce7.

When a Package label is voided, the corresponding Fulfillment status update will be removed from Commerce7.

In the attached image you can see an example Commerce7 Order. There are multiple Fulfillment lists under the Fulfillment tab. There is one for each Printed Package. Before any Packages are printed the Order’s Status is “Not Fulfilled”. After at least one package is printed, but not all associated packages are Printed, the status will be “Partially Fulfilled”. Once all associated packages are printed the Order will be “Fulfilled”.

Commerce7 SKUs are case-sensitive

Commerce7's SKUs are case-sensitive, so if a SKU entered in FORT is different from that entered in C7, the tracking numbers for the packages with that SKU cannot be uploaded to C7 (as the SKU contents will not match).





  • Splittable Virtual Kits cannot be used for C7 orders. If a splittable kit is uploaded, the system will generate an error: "Splittable Virtual Kits cannot be used for Commerce7 orders. Please update Item ID: kit_Id's "Splittable" field to No and then try to import again. Otherwise you will need to manually upload the order."
  • Commerce7’s system is case sensitive, even for SKUs. C7 doesn’t require using just caps or just lower case. You can any combination of caps or lower case letters, but however they are used, what is entered in FORT must match exactly what is entered in C7.
  • All orders that have not been modified in over 30 days will be ignored.
  • FORT imports products that don't have "Shippable Product" set to false. FORT does import C7's "Bundled Products" which are equivalent to FORT's "Virtual Kits", even if they have non-shippable products.

Note that Commerce7's platform does not capture the Recipient Email or Phone number, and we do not anticipate that it will at any time soon. According to the Canadian-based Commerce7, Canadian privacy laws prohibit marketing to a recipient who did not place an order by him or herself, and thus, Commerce7 does not save recipient phone or email data to ensure compliance with such regulations. Unfortunately, without this information, shipment status emails would not be sent to a recipient unless the recipient information is manually entered into FORT via a batch file or directly into the order detail page.














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