Shipping Labels

Context

To map an existing data source for Shipping Label data, Orderful’s NetSuite Connector leverages user-generated Analytics DataSets. This allows each individual customer to create a direct mapping from their existing custom data to required for Orderful’s label API endpoint.

Custom Label Source

Dataset Requirements

When creating the label dataset, pay close attention to the labels of each column as these must match expected values (not case sensitive).

One primary column is always required:

Fulfillment: this is the internal id of the item fulfillment we will be generating a label from

As we leverage the existing Orderful Label API, the remaining requirements can be found on our Orderf Label Requiremens page. Here you can see the required and optional columns for supported labels. You can also find the ID for the specific labels you need for each partner.

When designing your dataset, you may use a single, consolidated dataset or create unique datasets per label if needed. The dataset column names should exactly match the label property including the decimal.

If your partner has different label requirements for pallets and cartons you may need 2 separate datasets.

Customer Setup

Once you have your dataset, you're now ready to configure your customer. For each unique label, we need to create a Label Data Source entry.

1. From the Customer, EDI setup tab, navigate to Order Management Config. See Enabeling Customers for EDI
2. Edit the Customer and select your Label Data Source or click new to generate a new entry.
   1. Carton Dataset ID The label template ID is sourced from Orderful’s label documentation: Generate a UCC-128 (GS1-128) Label where a user can click on “SEE LABEL TEMPLATE LIBRARY HERE” (links to this page here) . For example, if you were setting up Carton labels for Cabelas, you’d choose CABELAS_CANADA_CARTON as the Carton Label Template ID.
   2. Pallet Dataset ID The ID of the dataset to use for pallet label information (if using pallet labels).
   3. Carton Label Template ID The Orderful Label Template name from the public labels guide for carton labels.
   4. Pallet Label Template ID The Orderful Label Template name from the public labels guide for pallet labels.
3. Save your Label Data Source entry

Generating the Labels

As long as there is a matching pair of either (Carton Dataset ID/ Carton Label Template ID) OR (Pallet Dataset ID/ Pallet Label Template ID) configured on the customer record, a new button will be shown on an item fulfillment that says Generate Labels (Orderful). Upon clicking this button, if the API call was successful, a new tab will open with the PDF of the labels open and ready to download. If there was an error, there should be a popup that opens with some details about what was wrong with the label payload.

Data Structure and Examples

Flat Data

All data provided must be flat. There will be one label generated per row, so it is up to the user creating the dataset to ensure that data is filtered as needed to conform to the correct standard.

Note: There is a maximum of 1000 labels currently supported by the bulk labels API in orderful.

No Required Filters

The dataset created to map packing data does not require any filters. However, due to the ambiguity of the data that could be used as a source for this dataset, if there are pre-defined filters that exist on the dataset, they will be retained, and combined with an AND filter with a filter on the fulfillment column, as labels are generated on a per-item-fulfillment basis.

Pallet And Carton Labels

If the customer in question requires both pallet and carton labels and those datasets are both created and configured properly, the returned PDF will have all the carton labels followed by all the pallet labels.