The generic shipping label is one of our Generic range of integrations, which essentially means it can be used by anyone as it is not tailor made to an exclusive use case and has the possibility to fit many. On the integration is has a field called Shipping Carrier, as the integration is generic it requires a carrier to be set to pull the orders in from. For example for the orders to be able to use the integration, the drop ship will need to set the integration up and the orders will need to have the shipping carrier set on the order that is defined in the integration.
Ahead of time is required to be enabled on the integration.
Like many other shipping integrations this integration provides the option for two separate data strategies currently, multi & single. The multi item data strategy will place each item in the order into a single shipment, whilst the single item data strategy will place each item into a an individual shipment.
Lastly, the html template is what makes the shipment unique, it allows the user to create their own shipment label. This has many use cases and allows them a lot of freedom and ways to pass labels through the system. This html is verified within the integration and will not create a label with invalid html.
When setting a HTML template, a <meta charset="UTF-8"/> tag can be added to the <head> element so that international characters are printed correctly.
To access certain elements of the order the html allows the user to access fields from the order, shipment and item level with the html tags {{ order.external_ref }} , {{ item.mapped_sku }}, {{ shipment.tracking }} for example, also here is a list of commonly used fields that may prove helpful:
- order.customer_name
order.shipping_address_1
order.shipping_address_2
order.shipping_address_3
order.shipping_address_4
order.shipping_address_5
order.shipping_postcode
order.shipping_country
order.sale_datetime
order.shipping_carrier
item.description
item.mapped_sku
item.quantity
item.unit_sale_price