Connect Tactical Logistics to Pipe17

It supports:

• Outbound flows: shipping requests and fulfillments

• Inbound flows: arrivals and receipts

• Core master data: products, inventory, locations

• Reverse logistics: returns

Tactical currently supports Amazon FBA orders. The connector assumes your primary use case is moving FBA inventory between Tactical warehouses, Amazon fulfillment centers, and other logistics locations.

Before you begin

• Make sure to have the email and password of the Tactical Logistics account.

Although the Integration uses Email/Password for authentication, the API calls are made using an API token that is generated using the Email and Password.

Connect Tactical Logistics

1. Sign in to the app.

2. Go to Connections → Add Connection → Tactical Logistics.

3. Enter your email and password for your account and click Connect.

Connector Flows

Product Sync

What it does

Important Notes

• Supports both product creation and updates, ensuring Tactical always has current SKU data.

• Includes a force sync option that pushes a full catalog refresh and then automatically disables itself.

• Uses the app’s standard product fields without any custom-field mapping.

• Should be enabled before using any outbound or inbound flows requiring SKU recognition.

Shipping Requests (Outbound Orders)

What it does

Important Notes

• Only Amazon FBA orders are supported for outbound shipping requests.

• FBA ID is cleaned using regex to remove unsupported symbols required by Tactical’s API.

• Key fields are mandatory, including Amazon FC, FBA ID, Amazon reference ID, and box count.

• This flow triggers order fulfillment at Tactical and should be enabled only when live order processing is intended.

• If Tactical deletes an outbound order, the app automatically marks the corresponding shipping request as canceled when fulfillments sync.

• Tactical does not support line-level cancellations; cancellation applies only to entire shipping requests.

Fulfillments

What it does

Important Notes

• Uses mappings consistent with shipping requests to maintain data alignment.

• Order notes are widely used in Tactical workflows and may be required for certain operations.

• Custom fields, such as delivery type, can appear and be saved for future reference.

• Carton labels are always required for outbound orders, though inbound orders may not require them.

• If an outbound order no longer exists in Tactical, the fulfillment sync will reclassify the related shipping request as canceled.

Inventory Sync

What it does

Important Notes

• Tactical does not support bundle inventory, so each SKU is handled individually.

• Inventory sync can be restricted to specific SKUs, allowing testing with selected items.

• The force inventory sync option performs a full refresh to correct discrepancies.

• Five-minute sync intervals ensure stock levels remain timely and accurate across channels.

Arrivals (Inbound Orders)

What it does

Important Notes

• Arrival flows represent inbound inventory and must use Carton to Amazon = 0; any value above zero converts the order to outbound classification.

• Required Amazon fields include reference ID, FBA ID, and Amazon FC.

• Arrival operations can be limited to specific PO IDs, enabling controlled testing.

• Tactical’s receipt process includes two statuses: Received or Move To Inventory, Move To Inventory Only.

• Receipt pulling occurs every five minutes to keep inbound inventory updated.

Returns

What it does

Important Notes

• Tactical requires returns to be explicitly identified through notes when pushing, ensuring the order is categorized correctly.

• Only the receipt portion of a return is updated in the app; original RMA data is preserved.

• Custom fields merge additively, meaning new data is added without overwriting existing details.

• Some warehouse IDs used in return workflows may be hardcoded, depending on Tactical’s operational configuration.

• Returns created directly in Tactical’s UI are recognized automatically using the return order type.

Connector Settings

Products Settings

Inventory Settings

Arrivals Settings

Locations Settings

Receipts Settings

Returns Settings

Troubleshooting

Shipping request is marked Canceled in the app

• Check whether the outbound order still exists in Tactical.

• If Tactical deleted it, the connector will mark it as Canceled during fulfillment sync.

• Recreate the outbound order in Tactical if needed and resend the shipping request.

Products are not appearing in Tactical

• Confirm products.out is enabled.

• Check if SKU filters are set; ensure the SKUs you expect are included.

• Use Force products resync if Tactical’s product data appears incomplete.

Inventory levels look incorrect

• Confirm inventory.in is enabled.

• Check SKU filters under inventory settings.

• Use Force inventory resync to refresh all quantities.

• Remember that Tactical does not support bundles; verify you are looking at individual SKUs.

Receipts are not pulling as expected

• Review the receipt status filter:

  • If set to Move To Inventory only, receipts that are only “Received” will not sync.

• Check the Events page for mapping or status errors.

Returns are not updating

• Confirm both returns.out and returns.in are enabled.

• For pushed returns, ensure notes clearly mark the order as a return so Tactical classifies it correctly.

• Remember that only the receipt side of the return is updated in the app, not the original return record.

Need Help?

If you need additional assistance:

• Use Ask Pippen, our AI agent, located at the top of the app page.

• Submit a support request with as much relevant detail as possible. Learn how to submit a request.

• For urgent issues, email us directly at support@pipe17.com.

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