Connect Logiwa: push orders out, check inventory

Use a Logiwa account email and password with API access in the WMS connection, test the real token sign-in, map, and activate — orders go to Logiwa and inventory can be checked.

The Logiwa connector connects this system to Logiwa as an external warehouse system. It can push shipment orders to Logiwa, in single or bulk form, and check inventory held in Logiwa. Shipment confirmations come back through the Logiwa Webhook V2, not through a polling call in this connection. This connection is configured in the WMS area, not through the channel wizard, and it signs in with a Logiwa username and password to obtain a session token.

Prerequisites#

• A Logiwa account you can sign in to. The username for this connection is the email of a Logiwa user who has API access.
• The password of that same Logiwa user. There is no separate API key to generate for this connection — the account email and password are the credentials.
• You know whether to use the default service address https://myapi.logiwa.com, or a different baseUrl given for your Logiwa setup. If nobody gave you a different address, leave the default.

Get your credentials#

1. Pick the Logiwa user for the integration and confirm that user has API access. Use a dedicated user where possible, so a personal password change does not break the connection.
2. Note the username: the email address of that Logiwa user.
3. Note the password of that same user. You will enter it once in the WMS connection, where it is stored as a secret and used together with the username to obtain a token.
4. If your Logiwa setup gave you a service address different from the default, note that baseUrl as well. Otherwise there is nothing else to collect.

Fill it into Integration#

This connection has no channel wizard field list. Open the WMS connection for Logiwa in Integration and fill in the values below on that WMS connection form. Do not look for Logiwa in the channel wizard field steps — the wizard has no fields for it.

1. username — required: the email of the Logiwa user with API access, exactly as used to sign in to Logiwa.
2. password — required: the password of that same Logiwa user. It is a secret field and is sent together with username when the system obtains a token.
3. baseUrl — optional: the Logiwa service address. Leave it empty to use the default https://myapi.logiwa.com, or fill in the different address given for your Logiwa setup.

Test the connection#

Use the test on the WMS connection. It sends a real sign-in request to the token address under your baseUrl, with the username and password you filled in, and it passes only when Logiwa returns a token. If username or password is missing, the test stops with MISSING_CREDENTIALS. If the request returns no token, it fails with AUTH_FAILED. There are two test entries you may come across: this WMS connection test is the real credential check described here, while a test shown in the channel wizard does not contact Logiwa with these credentials — do not treat a pass there as proof that the Logiwa account works. Judge the connection only by the WMS connection test.

Mapping / pick a template#

Pick the Logiwa standard mapping. With it, an outbound order in this system becomes a Logiwa shipment order, and an inventory check reads the Logiwa inventory list for the mapped SKU. After the test passes, push one real order and compare it in Logiwa — order reference, lines and quantities — and check one SKU quantity against what Logiwa shows, before activating. If a SKU in this system names the same product differently in Logiwa, fix that SKU in the mapping instead of renaming the product in either system.

Activate#

After activation, outbound orders from this system are pushed to Logiwa as shipment orders, one by one or in bulk, and inventory checks read the current Logiwa quantities for the mapped SKUs. Shipment confirmations come back through the Logiwa Webhook V2, so keep the webhook delivery working on the Logiwa side. Watch the first orders in Runs / Logs and in Logiwa itself before leaving the connection unattended.

FAQ#

WMS test fails with AUTH_FAILED

The token request reached Logiwa but returned no token. The username and password pair was not accepted: the email is not a Logiwa user with API access, the password does not belong to that user, or the baseUrl points to a different Logiwa environment than the account belongs to.

Sign in to Logiwa in the browser with the same email and password to prove the pair works, confirm the user has API access, then re-enter username and password in the WMS connection with nothing trimmed. If a different baseUrl was given for your setup, set it exactly; otherwise clear baseUrl so the default address is used, and test again.

Test stops with MISSING_CREDENTIALS

username or password is empty on the WMS connection. The token request needs both values, so the test stops before contacting Logiwa.

Fill in both fields on the WMS connection form — username with the Logiwa user email and password with that user password — save, and test again.

The channel wizard test passed, but the WMS test still fails

The two tests are not the same check. The channel wizard has no Logiwa fields and its test does not sign in to Logiwa with your username and password, so a pass there says nothing about the Logiwa account. Only the WMS connection test performs the real token sign-in.

Ignore the wizard result for this connection. Run the test on the WMS connection and work from its result: MISSING_CREDENTIALS means a field is empty, AUTH_FAILED means the account pair was refused.

Orders push, but Logiwa shows different quantities

The connection and the token work — the order arrived — but a line does not match: usually the SKU on the order names a different product in Logiwa, or the unit on the line differs between the two systems.

Compare the pushed order line by line with the order in Logiwa, fix the SKU mapping for the mismatched product in the mapping, then push a fresh test order and compare again before resuming normal orders.

Inventory check returns nothing for a SKU that exists in Logiwa

The inventory check reads the Logiwa inventory list with the mapped SKU. If the SKU sent is not the SKU Logiwa holds the stock under, the list comes back empty even though the product exists.

Find the exact SKU on the product record in Logiwa, set that value in the mapping for this product, and run the inventory check again.

Orders ship in Logiwa, but no shipment confirmation arrives here

Shipment confirmations for this connection travel through the Logiwa Webhook V2, not through the order or inventory calls. If the webhook delivery on the Logiwa side is stopped or failing, orders and inventory keep working while confirmations stop arriving.

Check the webhook delivery status on the Logiwa side and restore it, then ship one test order in Logiwa and confirm the confirmation arrives here before resuming normal volume.