Generic Shipping Label

Generic Shipping Label

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:
  1. order.customer_name
  2. order.shipping_address_1
  3. order.shipping_address_2
  4. order.shipping_address_3
  5. order.shipping_address_4
  6. order.shipping_address_5
  7. order.shipping_postcode
  8. order.shipping_country
  9. order.sale_datetime
  10. order.shipping_carrier

  1. item.description
  2. item.mapped_sku
  3. item.quantity
  4. item.unit_sale_price


    • Related Articles

    • Shipper Integration | Generic Label

      Introduction This article has been created to show how to setup the Shipping Integration that Kornit X has built to connect to a Generic Label. Setup To setup the Generic Label integration, please head to your company and within the advanced settings ...
    • Notification Integration | Generic Filesystem

      Introduction This article has been created to show how to setup the Notification Integration that Kornit X has built to connect to a Generic Filesystem  Setup To setup the Generic Filesystem Notification integration, please head to your company and ...
    • Product Integration | Generic API

      Introduction This article has been created to show how to setup the Product integration Kornit X has built to connect to Generic API.  Setup To setup the Generic API integration, please head to your category and within and within the advanced ...
    • Production Integration - Generic API

      Introduction The Generic API production integration pushes batch data and related order data, in JSON format, to an API endpoint.  The integration makes it easy for fulfillers with in-house developers, to ingest this data and produce jobs outside of ...
    • Supplier Integration | XML (Generic Filesystem)

      Introduction This video covers our XML supplier integration where we can pass orders details from OMS to an external system in an XML Format. We also call this integration "Generic Filesystem".  For more information, please refer to this developers ...