Skip to content

Shipping

The shipping function of the Inventory micro-cap supports a store associate with processing shipping documents and updating the inventory system with the shipped items. Shipping supports the following document types: - RTW (Return to Warehouse) - Transfer Out (to another store) - RTV (Return to Vendor)

Architecture

Shipping documents are created centrally by a source system and sent to the Inventory shipping API. The Inventory shipping API processes the document and updates the Inventory system with the received items. The Inventory shipping UI allows store associates to view and complete the shipping documents. When a document is completed, the Inventory shipping API sends a message to the Webhook, which publishes an Inventory Control Document to subscribers of SHIPPING messages.

flowchart LR
    integration("`Integration`")
    shippingAPI("`Inventory Shipping API`")
    jmcClient("`JMC Client`")
    webhook("`Webhook`")
    integration -- Create Document--> shippingAPI
    shippingAPI --> jmcClient
    jmcClient -- Complete --> shippingAPI
    shippingAPI -- Control Document --> webhook
    webhook -- Publish --> integration

Configuration Data

The following tables are used to configure the Inventory shipping function:

Table Purpose
inv_vendor third-party suppliers of merchandise sent or received by a store
car_label_printer mapping of printer and their label types to their ip location (label_type must be "zpl-shipping-label" and protocol should be "zpl-printer")