Shipstation FAQs

For each retailer connected through Logicbroker, you can create your own custom sales channel in Shipstation. The StoreID from Shipstation will need to be provided for each retailer you are connecting. This must be included in the survey or by contacting Logicbroker Support.

For all orders requiring a packing slip, the link will be provided in the "Internal Notes" field in Shipstation. Clicking it will take automatically download the form in PDF format. **Note you must be logged in the Logicbroker portal.

If you are looking for an automated approach to downloading packing slips they can also be provided via SFTP/FTP location. Contact support@logicbroker.com for more details on setup. **This may require an upgrade in your account.

Note: Logicbroker offers professional services in helping map packing slips using the standard Shipstation workflow. Contact support@logicbroker.com for more details. **This may require an upgrade in your account.

If you are integrating with a retailer ordering for replenishment or in-store pickup, you may be required to provide a GS1-128 label on your packages. The information sent to the retailer will have the bar code number matching the label.

In this case, Logicbroker will create the bar coded numbers for each package created in Shipstation, but will require the printing of the labels in the Logicbroker portal. To auto-create the barcodes, you will need to contact support@logicbroker.com and provide your GS1 Company Pre-fix. For more information on the company pre-fix see this link.

To print the label, create the shipment in shipstation as normal, search for the shipment in the Logicbroker portal, and on the shipment details page > click More Actions > View GS1 Label. You will be provided with the option to print in PDF, PNG, JPEG, Zebra file, or Postscript.

The label on each container must match what is sent; the retailer will use this to scan to match the data sent on the ASN document. If these are not sent, they may result in a chargeback.

Cancellations are pulled from Shipstation when they are cancelled. To default a specific cancellation code, select one of the standard Logicbroker cancellation codes on the on boarding survey; the list is also provided below.

• Administrative request
• Bad address
• Cancelled at retailer's request
• Cannot fulfill in time
• Cannot ship to PO box.
• Cannot ship using provided ship method
• Customer changed mind
• Discontinued item
• Duplicate order
• Fraud detected
• Info missing on purchase order
• Invalid SKU
• Invalid ship method
• Item recall
• Other
• Out of stock
• Invalid item cost

There are 2 options to send standard accepted acknowledgements.

Acknowledgements can be created manually using the Logicbroker portal. Or it can be setup to send acknowledgements automatically based off of the order. For every order received an accepted acknowledgement will get created and sent to the sales channel automatically. From the on boarding survey make sure this feature is selected to have this automation enabled.

When filling the on boarding survey, you can select how many days you are expected to ship an order. This will default on all auto-created acknowledgements.

Returns will be used to send to a retailer when a physical return is received and you are requesting credit. These can be created in the portal manually given the retailer has the ability to receive this document type.

Like acknowledgements, invoices can be created in the portal manually, one at a time, using a CSV bulk upload, or automatically creating them off of the order or shipment.

Creating the invoices in the portal, you can create them off of a shipment or create it using the order. When creating off of the shipment only the items from the shipment will be provided, and no other lines can be added. When creating off of the order, all items will be available and normal invoice quantities can be selected.

To auto-create the invoices, the setup information will need to be provided in the on boarding survey. You can auto-create off of the shipment or order; both will use the pricing information provided on the order.

In this case, a shipment will need to get created to initiate the routing request to the retailer. You can create the shipment in Shipstation and when Logicbroker pulls it, will send the routing request. At this point, the 754 (routing instructions) will await being received; this will include all details such as pickup date, tracking numbers etc. You can subscribe to the "Routing instructions" notification to receive the details in email.

Once the 754 (routing instructions) is received and the the carrier picks up the shipment, the ASN/shipment can be submitted; to do this navigate to the shipment in the LB portal and click "Complete Shipment"

Inventory is not pulled from Shipstation, all inventory information will need to be submitted in the Logicbroker portal. This will need to be submitted on a normal cadence according to your retailer's requirements.

Logicbroker can also receive automated inventory feeds by receiving CSV or EDI. See this article for more details on setting that up.

Regardless, of method all inventory items will require a setup process, instructions can be followed here. 

**Logicbroker also offers a connection with SKUVault-shipstation which automatically pulls inventory and broadcasts it to all retailers and sales channels.

During the setup process as shown here,

You are required to setup a MerchantSKU and SupplierSKU link; this link can be used to update your orders with the setup SupplierSKU. When an order is received, the OrderLine.ItemIdentifier.PartnerSKU will be used to lookup the SupplierSKU to update the order. This will make sure that all orders that are pushed into Shipstation have a valid item.

You will need to make sure that all Shipstation SKUs are setup in Logicbroker including the mapped MerchantSKU.

Orders are sent to Shipstation as they are received from the retailer/sales channel. There is no scheduled process.

By default Logicbroker will be set to pick up shipments every hour at the 5th minute.

Below are the list of codes that map from Shipstation to Logicbroker. These will be used to communicate from (orders) and to (shipments) you retailers.

All retailers on Logicbroker have a standard code they map to and this is managed by Logicbroker. If a code is received or sent that isn’t in the list below, the order will create in Shipstation with the unmapped value received from the retailer.

From inside Shipstation, the method can be mapped so handling can be automated for future orders. For more information on shipment mappings in Logicbroker see this article

40 requests per minute. This is a hard limit set by Shipstation and their support would need to be contacted if the limit is reached.

If there is an error in sending orders to Shipstation, you will receive an error notification via Email and the Order document will move to a Failed status. The error notification will contain all details in regards to the error and if needed the document can be reset. You can view the event in email or portal - see details about notification events here.

Typical errors include - 

• Missing SKU in Shipstation: Add SKU in Shipstation and retry order. 
• Unmapped SKU in Logicbroker: Add SKU to Inventory Feed setup and retry order.
• Connection Error: Retry order.

For documents (Acknowledgements, Shipments and Invoices) going outbound to retail channels, the same notifications will be present both via email and portal, including the changed status to "Failed" 

Logicbroker has standard validation to prevent in-compliant data to your retail channels, however there may be cases where errors are data related for example a wrong tracking number for the ship method. These errors will be provided via message from the retailer. If one is received you can create a ticket to support@logicbroker.com or through the help center.

Logicbroker provides standard reporting using configurable tiles, bar charts and donut charts. For more information on setting up reports see this article.

In addition, document CSV/XSLX exports are accessible as well; see this article for more details.

Additional integrations through the Logicbroker API will not be supported. We do offer service to build custom integrations, to learn more contact sales@logicbroker.com

There are 3 custom fields available in Shipstation. These can be mapped from any Logicbroker order field, you can provide details on the on boarding survey. For more detail in regards to field mappings see this article.

You can test by connecting your Logicbroker stage environment (stageportal.logicbroker.com) to your production Shipstation if you do not have a separate Shipstation account.

From there you can test your integrations using the Logicbroker testing process; see this article.

Under Testing you can simulate production by creating test orders for each retailer you are connected to. This will send the orders to your Shipstation where you can fulfill, Logicbroker will then pull and validate against the retailer's requirements.

**Note if you are testing in production shipstation account, the test orders will be identified with a "TEST" prefix.