Summary: A batch fails when the Merchant app (the small app on the shipping PC that links the station to Shipstore) is not logged in or the station shows NOT LINKED. Log into the Merchant app with the same username as Shipstore and confirm the station is Linked, then reprocess.
Problem
A batch fails (sometimes several times in a row) with a log message like:
Unable to find Merchant login by [user]
Or a shipment errors because the station shows NOT LINKED when it tries to send data back to your integration. The common thread is that the Merchant app is not logged in or linked as expected.
Cause
When the Merchant app is not logged in, or the station is not linked (or is signed in under a different username than Shipstore), Shipstore cannot match the Merchant login for the run, so the batch or shipment errors. A non-integrated batch set to PDF mode does not need a linked station, so linking only matters when your workflow uses the Merchant app or an integration.
Fix
- Open the Merchant app on the shipping station and log in with the same username and password you use for Shipstore.
- Confirm the station shows as Linked, not NOT LINKED.
- If it keeps failing, fully log out of both the Merchant app and Shipstore, then log back into the Merchant app first, and reprocess.
- For a non-integrated batch, set the run to PDF mode; the station does not need to be linked in that case.
What you should see
The station shows Linked and the batch or shipment processes without the "Unable to find Merchant login by" error. Data posts back to your integration where that applies.
Related articles
- No station appears or NOT LINKED when you load an order
- Merchant App is down or all stations time out at sign-in
- Batches or imports stop: a Shipstore service is not running