Carriers
Add carriers or couriers you will use to transport goods to track them in sales and purchases.
Note: If you are using a shipping service such as ShipStation and Shippit, the carriers are imported automatically from the shipping service. See Shipping and Fulfillment for more information.
Add carriers and tracking URLs
Carriers in Cin7 Core are managed from Settings → Reference Books → Other items → Carriers. You can include a tracking URL for each carrier, which will be used to add tracking links to your documents.
Add a new carrier:
Navigate to Settings → Reference Books → Other items → Carriers.s
On the Carriers page, click + or Add more items.
Add the Carrier name and a tracking URL if applicable, then click Save. The Tracking URL for a carrier should be available on its website or help documentation, if you are having trouble finding the Tracking URL for a carrier, please get in touch with their support for help.
Enter the Tracking URL if applicable in this format (http://www.royalmail.com/portal/rm/track?trackNumber=). When you press Enter, Cin7 Core will automatically add [TrackingNumber] to the end of the URL.
Add Carrier and Tracking Number to Sales
Specify Carriers for your shipments on the Ship tab of the sale process. You will be able to select carriers that you have previously entered in your Reference Books. If you have received a Tracking Number from your carrier for the shipment, you can enter it here. This will be added to the Tracking URL specified above to add tracking links to your documents.
Note: If you are using an external shipping service, the carrier and tracking number information will be imported automatically from the shipping service. See Shipping and Fulfillment Services for more details.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB