Kustom Shipping Assistant (KSA) can display nShift Delivery's shipping options at checkout, but the customer's choice is not a complete shipping booking in itself. You need both the KSA connection and Abicart's nShift integration to finalize the correct shipment. Before setting up, ask support to confirm which subscriptions, add-ons, and carrier agreements are required for your specific store.
Activate and connect KSA and nShift Delivery, which may be called Unifaun Online in the Admin.
Let the integration use KSA's TMS reference to finalize the correct prepared shipment.
Choose stored or direct booking and decide separately when the order should be marked as shipped.
Follow an agreed-upon test order from shipping option to the same reference in nShift. Check the booking, label, and any customer notification separately.
Which connection does this guide apply to?
This guide applies to KSA together with nShift Delivery. It does not describe nShift Transsmart, Webshipper, or a workflow where an ERP system handles the shipping booking. First, confirm which path your order actually uses.
You need a working KSA connection, nShift Delivery with the intended transport services, and Abicart's corresponding integration. Read the overview for KSA and connect nShift Delivery if the basic connections are not yet ready. The inclusion of a general transport integration in your package does not automatically confirm that all parts of this setup are included.
Understand the workflow
nShift's delivery options and any pickup points are displayed via KSA at checkout.
The customer selects shipping and completes the purchase. The choice is linked to a prepared shipment and its reference.
Abicart's nShift integration uses the reference to finalize the correct shipment according to your booking settings.
You check the booking and shipping documents in nShift. Abicart's shipped status and customer messages are handled according to their own settings.
See image details: open a screenshot in a separate tab or window using your browser's image menu if the text is too small.
This is an example of shipping options at checkout. A message that an address or pickup point is missing must be resolved before a complete selection can be made.
The flowchart shows why both a shipping selection and a subsequent finalization of the shipment are needed. There is no fixed percentage to show how complete each order is.
1. Connect and use the correct reference
Check KSA and the transport services to be offered in nShift. Connect the Abicart shipping method that will handle KSA to the correct connection; the basic example uses such a method.
Go to Settings > External Connections > Unifaun Online.
Check the basic settings according to the nShift guide. Activate use_tms_ref_as_prepared_id, which may be displayed with this technical field name. This allows the export to use the TMS reference from KSA's prepared shipment.
Save. A missing reference or one that points to the wrong shipment should be investigated before exporting the order again.
Check the reference before exporting. Verify that the current order has the correct KSA/TMS reference. An activated setting does not automatically stop an export that lacks a reference; in that case, a regular shipment might be created using the integration's transport service and recipient details instead of the saved KSA selection. Investigate the reference and check existing shipments before exporting or retrying. In particular, check how the reference should be used if the order has multiple shipments.
2. Select booking and shipped status
Option | What it means | What to do afterward |
Booking: Stored | The shipment is saved for further handling in nShift. | Check details and any return handling before you finalize the booking and print shipping documents. |
Booking: Direct | The export requests a direct booking according to the connection's setup. | Check the booking result and documents. Do not expect to be able to change the service or return option after booking; the allowed handling depends on the service. |
Shipped: Never | The order is not automatically marked as shipped upon export. | Mark the order as shipped when dispatch should actually be confirmed. This gives you control when shipments are stored first. |
Shipped: After export | A successful export can also mark the order as shipped. | Check that this matches your workflow. A delivery email may be sent if it is activated under Document and email content. |
A label that is available for printing does not in itself indicate that the package has been handed over to the carrier. Similarly, an order marked as shipped does not in itself indicate that the nShift booking is correct. Check both results.
3. Choose when to export the correct order
Open the shipping method used for KSA on the integration page, in the image example Shipping.
Go to Event Settings > Export order.
Select trigger: Reserved to export when the order is registered, Paid when it is marked as paid, or Manual for your own export: go to Orders > Orders and open the correct order. Find nShift/Unifaun Online among the order's external services and use the connection's export action. First, check the existing shipment and TMS reference to avoid creating a duplicate.
Select an intended Transport service; do not leave the field empty. Do not assume that an arbitrary choice is always harmless just because KSA is used. Check with the person responsible for the connection how the selection and the KSA reference interact in your setup.
Save and follow a limited test order before using automatic export widely.
The images illustrate automatic export with a stored shipment. In this setup, the booking needs to be finalized in nShift before printing/sending according to your workflow. Check the transport service, address, pickup point, and any return before finalizing.
Return label, print favorite, and notification
If you want to prepare a return label, check the service's support and select the correct return/round-trip handling before the shipment is booked. Ask nShift for help with service-specific requirements. Do not assume that an already booked shipment can be edited or supplemented in the same way as a stored one.
A print favorite in nShift can group selections for things like a return label and SMS notification where the service supports it. In the English interface shown in the images, you go to Maintenance > My Account > Settings and select change next to other settings. Enter the favorite's exact name in order favorite and save with finish. Menu texts may differ between versions.
Here, the favorite name order is an example. Use the name of the favorite you have actually created.
Check results and troubleshoot
Symptom | Check and next step |
Shipping options are missing at checkout | Check the KSA connection, delivery address/pickup point, and which nShift services are available to the customer. Do not go directly to label settings. |
Prepared shipment exists but no booking/label | Check that the order has met the export condition, that the correct TMS reference is included, and if the shipment is stored pending finalization. |
Wrong shipment or risk of a duplicate | Compare the Abicart order number, TMS reference, and existing shipment before a new export. Do not create an extra shipment as the first solution. |
Customer received the delivery email too early | Check 'Shipped: After export' and the document/email settings separately from the booking mode. |
Shipping document or return is missing after booking | Check the service, booking status, and documents in nShift. Contact nShift for the service's return and printing conditions. |
When contacting support: specify the store, actual integration path, order number, TMS reference, time, selected booking mode, and error message. State whether a shipment or label has already been created. Do not send integration passwords.