Connect fulfillment providers

Fulfillment providers, also called 3PLs, receive your shipments and report tracking, products, and stock back. You add these accounts in Settings → Connections, where they appear under Fulfillment providers.

Connecting an account never starts sending shipments. That happens per location in Fulfillment → Setup, and only for workflows that you switch to Active.

Provider	What you enter	Guide
JTL FFN	Your own JTL app, then a sign-in at JTL	Connect JTL to the hub
Magware	API URL, owner code, and API key	Magware
Mintsoft	API key	Mintsoft
Logisoft (Asendia)	Customer reference and API token; optional SFTP drop for invoices	Logisoft (Asendia)

Before you begin

• Have the provider’s connection details ready. Request them from the provider if needed.
• Enter API keys, tokens, and private keys only in the hub’s form. Balta Labs stores them encrypted and never shows them again. Never send them by email or chat.
• You need the Connections permission in the workspace.

Add an account

1. Open Settings → Connections. Under Fulfillment providers, select Add provider. Add account at the top of the page lists the same providers.
2. Choose the provider.
3. Optionally enter a Connection name, then fill in the fields described below.
4. Select Save account.
5. Select Test on the account card. Correct the values until the card shows Working.
6. Select Details to see the Account, What the hub can do, and the Reference lists that you choose from when you set up locations.

To change an account later, select Edit on its card. Leave a secret field blank to keep the stored value. Changing credentials or addresses resets the health to Not checked until the next test.

Magware

• API URL: the address of the Magware API, as given by your warehouse, for example https://wms.example.com/api/. It must be a public address without user names, query strings, or # parts. http:// works if your Magware server offers nothing else, but prefer https://.
• Owner code: your client code in Magware.
• API key: the key for that owner code.

Test reads the stock list and changes nothing in Magware. If the address does not answer like the Magware API, the test says so. Magware locations need no provider settings.

Magware returns each shipment update only once. The hub reads this consuming feed when Tracking is Active; it is not polled in Shadow mode.

Mintsoft

• API key: the Mintsoft API key of your client account.

Test lists the warehouses and courier services that the key can see, and Details shows them with their IDs. When you add the location, enter the Mintsoft warehouse ID, the Courier service ID, and the Prime courier service ID, which is used for Amazon Prime orders.

Logisoft (Asendia)

• Customer reference: your customer number at Logisoft.
• API token: your Logisoft API token.
• Advanced settings (optional): Core service WSDL URL (default https://soap.myasendia.it/LogisticService.svc?wsdl), Logistics service WSDL URL (default https://soap.myasendia.it/Service.svc?wsdl), and Timeout (seconds) (default 120). Change them only if Logisoft gave you other service addresses or asks for a longer timeout. WSDL URLs must use https://, and the timeout can be 10 to 300 seconds.

To upload invoices, also fill in the SFTP drop (optional): SFTP host (the host name only, without sftp://), SFTP port (22 by default), SFTP username, and SFTP private key (the whole key, including the BEGIN and END lines, in OpenSSH, PEM, or PuTTY format). The SFTP drop needs a host, a username, and a private key, or none of them.

Test checks the token, lists your stores, and reaches the logistics service. With the SFTP drop, it also signs in and checks the invoice folder. On the first successful test, the hub pins the SFTP server’s key. The card then shows SFTP host key pinned, and the hub only talks to a server with that key. If you change the host, the next successful test pins the new server’s key. If a later test reports a different key for the same host, confirm with Asendia that the change is expected, then contact support.

When you add the location, the Carrier code and Store code default to ASENDIA_IT and CUSTOM.

What health means

Health	Meaning	What to do
Working	The last test or provider request worked.	Nothing.
Check failed	The last test or request failed. The card shows the provider’s message.	Fix the cause, such as an address, network, or setting, then select Test.
Reconnect needed	The provider rejected the credentials or the authorization.	Select Edit and enter new credentials, or Reconnect a JTL account, then select Test.
Not checked	The account is new, or its credentials or addresses changed.	Select Test.

The card also shows when the account was last checked. The health changes when you select Test and when the hub works with the account. It describes the account, not individual shipments: check those in Fulfillment → Operations.

Enable warehouse workflows

In Fulfillment → Setup, add a source account and a location linking its warehouse to a connected provider. Configure schedules and manual jobs under Sync. Manage order rules and their account’s automation mode in Automations.

Use Shadow to inspect decisions, then switch the required workflows to Active. Changes to or from Active ask for confirmation and are recorded in the mode history. Review results in Operations, stock differences and product mappings in Inventory. To pause a workflow, choose Off or Shadow and inspect work already in progress in Operations.

To change several locations, select their rows, choose a workflow and mode, then select Review changes. The result lists any locations that could not be changed. Each source account has its own rules, saved drafts and activation history.