| show | logistics_inventory_report | Warehouse Management | Message that supports the inventory management process and enables a party to request an inventory report from another party, using specific selection criteria. |
| show | logistics_inventory_report_request | Warehouse Management | Message that supports the inventory management process and enables a party to report on inventory status and events as registered in his system. |
| show | warehousing_common | Warehouse Management | This package contains the components that are determined to be common to the Warehousing messages and helps to enforce consistency across them. |
| show | warehousing_inbound_instruction | Warehouse Management | Message that supports the warehouse inbound process, and enables a Logistic Services Client (LSC) to inform his Logistic Services Provider (LSP) that goods will be arriving. |
| show | warehousing_inbound_notification | Warehouse Management | Message that supports the warehouse inbound process, and enables a Logistic Services Provider (LSP) to inform his Logistic Services Client (LSC) on the status of goods received on behalf of the client. |
| show | warehousing_operations_common | Warehouse Management | This package contains the components that are determined to be common to the Warehousing Operations messages and helps to enforce consistency across them. |
| show | warehousing_operations_instruction | Warehouse Management | Message that supports the inventory management process, and enables a Logistic Services Client (LSC) to inform his Logistic Services Provider (LSP) that the inventory status of goods needs to be changed.
|
| show | warehousing_operations_notification | Warehouse Management | Warehousing Operations Notification – Message that supports the inventory management process, and enables a Logistic Services Provider (LSP) to inform his Logistic Services Client (LSC) that the inventory status of goods has been changed. |
| show | warehousing_outbound_instruction | Warehouse Management | Message that supports the warehouse outbound process, and enables a Logistic Services Client (LSC) to inform his Logistic Services Provider (LSP) that goods need to be shipped. |
| show | warehousing_outbound_notification | Warehouse Management | Message that supports the warehouse outbound process, and enables a Logistic Services Provider (LSP) to inform his Logistic Services Client (LSC) on the status of goods shipped on behalf of the client. |
| show | advanced_remittance_notification | Pay | The Advanced Remittance Notification is sent by the buyer to the seller upon reception of goods. The intent of the Advanced Remittance Notification is:
1. for the buyer to indicate the payment that will be made for goods actually received;
2. to communicate discrepancies that exist between the seller’s shipping documents and the buyer’s receiving documents
|
| show | application_receipt_acknowledgement | Other | The Application Receipt Acknowledgement message enables a message recipient to confirm that he received the message and whether he was able to process it without error. In this way the message helps to ensure a reliable flow of information between companies. |
| show | artwork_content | Other | The Artwork Content message enables to send the product’s artwork content that appears on a package (e.g. box, label, bag) or related materials (e.g. printed coupons). |
| show | artwork_content_common | Other | This package contains the components that are determined to be common to the Artwork Content messages and helps to enforce consistency across them. |
| show | artwork_content_response | Other | The Artwork Content Response message facilitates electronic exception reporting upon processing of an Artwork Content message. |
| show | buyer_reconciliation_of_request_for_payment | Pay | The Buyer Reconciliation Of Request For Payment is a message that allows a buyer to respond to Requests For Payment either submitted individually or assigned to a batch, from a seller. The document reports to the Seller whether or not the Buyer was able to schedule the Requests For Payment to be paid through the accounts payable system. |
| show | claims_notification | Pay | Claims Notification is a message sent by the buyer to the seller or vice versa for negotiating the resolution of claims. It may be used to:
1. communicate claims related to discrepancies that are first captured in the Advanced Remittance Notification,
2. communicate any other type of claim related to the specific shipment covered by the Advanced Remittance Notification, or any other additional type of claim made by either party.
|
| show | configure_to_order | Order | The Configure to Order provides the ability for a buyer to order configurable items, that starts with a base item, but to which a large variety of options may be added in a variety of combinations.
A unique product identification code is assigned to the main structure of a configurable item, but due to the variety of combinations of options, it is NOT practical to assign unique product identification to each completed configured item. |
| show | consumption_report | Deliver | The Consumption Report message enables the buyer needs to communicate the consumed products (e.g. used materials or sold goods) to the seller.
This information is required in consignment stock scenarios, where the invoice will be based on the consumed quantities rather than on the delivered quantities. |
| show | debit_credit_advice | Pay | The Debit Credit Advice message provides an electronic advice to a trading partner that a monetary adjustment - debit or credit amount value - is being applied to the purchase of goods or services, resulting in a change to the monetary amount owed/due between the parties. Situations such as (but not limited to):
- goods being received damaged
- incorrect quantity of goods are received
- retroactive volume discounts
Result in the need for one party to notify the other trading party that an adjustment is being applied, resulting in a change to the monetary amount owed/due between the parties.
For tax reasons the seller may need to issue a credit invoice to formally communicate the change including related taxes. |
| show | despatch_advice | Deliver | The Despatch Advice enables a shipper to provide information about the content of a shipment to a receiver. Usually the Despatch Advice serves as a pre-announcement of the goods being shipped. In a pick-up scenario it may also serve as a pre-announcement of goods to be collected.
Despatch Advice can also be used in a cross-docking delivery. |
| show | ecom_common_components | Common | This standard contains the components that are determined to be foundational to the eCom domain and helps to enforce consistency across messages. |
| show | goods_requirements | Plan | Goods Requirements is a message that enable the buyer to inform the seller about the requirement for given trade items and locations for specific time periods.
It may be used in traditional order driven scenarios and is definitely needed in supplier managed inventory scenarios, in combination with the Inventory Report. |
| show | goods_requirements_response | Plan | Goods Requirements Response enables the responding party to communicate the acceptance of the Goods Requirements transaction. |
| show | gs1_identification | Common | A subset of Shared Common package defining the components representing GS1 Keys and additional identifiers. |
| show | inventory_report | Deliver | The Inventory Report message enables a party (the inventory reporting party) to provide information on inventory levels and inventory changes to another party (the inventory report to party).
The Inventory Report may be used to provide information on buyer inventory in case of supplier managed inventory, but also can be used to provide information on available stock at a seller. Also it can be applied by logistic service providers to provide information on the available stock to their client. |
| show | invoice | Pay | The Invoice message is sent by the supplier to the customer claiming payment for goods or services supplied under conditions agreed by the seller and the buyer.
The seller may invoice for one or more transactions referring to goods and services related to one or more order, delivery instruction, call off, etc. The invoice may contain references to payment terms, transport details and additional information for customs or statistical purposes in the case of cross-border transaction. |
| show | item_data_notification | Align | The Item Data Notification provides the ability to align item master data in a peer to peer environment. The message support both the exchange of “General Item information” which is relationship independent, as well as “Specific Item information” which is relationship dependent.
The message will often be sent by the manufacturer or supplier of the item, but also may be sent by the customer (for example in cases where the customer owns the product design). |
| show | meat_despatch_advice_line_item_extension | Deliver | Meat Product Extension is an extension to the Despatch Advice Document used to enable tracking & tracing (traceability) of beef products. |
| show | order | Order | The Order provides the ability for a buyer to order specified quantities of goods and services from a seller for a single shipment to or from a single location.
The Order may be used alone when the buyer and seller have aligned data such as parties, item, pricing, payment terms, etc., prior to order creation.
The process is simplified by having one order placed for one delivery for one location at one time. |
| show | order_response | Order | The Order Response provides the ability for a supplier to respond to an order previously sent by the buyer.
The Order Response allows the seller to inform the buyer about:
- The acceptance of the entire order as transmitted or
- The acceptance of the order with modifications on items (substitutes), quantities, prices and or dates or
- The rejection of the entire order.
The same Order Response is used to respond both to the Order and Configure to Order messages. |
| show | performance_measurement | Plan | The Performance Measurement message allows trading partners to identify goals for the measures that that they wish to share, as well as exchange the values for those measures. The scope of the message includes key measures of Sales, Operations, Supply Chain, and Data Accuracy performance. |
| show | product_recall_closeout_notification | Other | Product Recall Closeout Notification enables the Product Recall Initiator to communicate that an earlier issued Product Recall Notification is no longer active / has been completed. |
| show | product_recall_common | Other | This package contains the components that are determined to be common to the Product Recall messages and helps to enforce consistency across them. |
| show | product_recall_notification | Other | The Product Recall Notification message notifies involved parties in the supply chain of the need to remove specific products (traceable items) which may pose a health and safety risk to consumers. |
| show | product_removal_confirmation | Other | The Product Removal Confirmation message enables involved parties to confirm which products (traceable items) they removed from the supply chain based on the request in the Product Recall Notification. |
| show | purchase_conditions | Plan | The Purchase Conditions message expressing the official commitment between buyer and seller that certain quantities are to be delivered over a given period and at the stated price. In doing so it sets the contractual conditions for the ordering and delivering of the goods and so details specific terms and conditions that apply for a given period.
The Purchase Conditions does not intend to contain the totality of the contractual information, but to provide the relevant data in order to be able to align key conditions in an automated way.
The Purchase Conditions message supports multiple scenarios:
- Fixed quantity and fixed period
- Fixed quantity and variable period
- Variable quantity and fixed period |
| show | receiving_advice | Deliver | The Receiving Advice enables the receiver of the shipment to inform the shipper on the actual goods received, compared to what was advised as being sent. |
| show | replenishment_proposal | Plan | The Replenishment Proposal message contains the seller delivery or production plan for the buyer for given trade items and locations for specific time periods. |
| show | replenishment_request | Plan | The Replenishment Request message contains the demand for given trade items and locations for specific time periods. The replenishment request contains both the goods requirements as well as the inventory status for each trade item and location. |
| show | request_for_payment | Pay | The Request for Payment message provides the core functionality for requesting payment for goods or services under conditions agreed upon between the seller and the buyer. |
| show | settlement | Pay | The goal of the Settlement message is to send payment instruction and / or remittance information. The remittance information can optionally include information on adjustments and/or discounts. |
| show | shared_common_components | Common | This standard contains the components that are determined to be foundational to all domains where GS1 XML is applied and helps to enforce consistency across messages. |
| show | transport_capacity_booking | Transport Planning | Transport Capacity Booking is the process to reserve space for estimated consignments or shipments. Typically the booking process covers a period of less than a week prior to actual shipments covered by capacity booking moving through the Logistics Network. The Logistic Services Buyer will send transport capacity booking requests to the Logistic Services Seller.
Capacity booking requests are used to reserve space prior to the goods being ready for despatch. At the point that the goods are actually ready to be moved and have been assigned a shipment or consignment identification, the Transport Execution process begins. |
| show | transport_capacity_booking_response | Transport Planning | The Transport Capacity Booking Response is sent by the Logistic Services Seller to the Logistic Services Buyer, accepting or rejecting the Transport Capacity Booking. |
| show | transport_capacity_plan | Transport Planning | The Logistic Services Seller is responsible for developing the Transport Capacity Plan. He does this based on the Transport Capacity Requirements communicated to him by the Logistic Services Buyer. The Logistic Services Seller may combine the cargo (for multiple requirement lines) if they are for the same trade lane (i.e. origin/destination), forecast bucket, and service requirement level (e.g. refrigerated vs. general cargo). |
| show | transport_capacity_requirements | Transport Planning | In the Transport Capacity Requirements message the Logistic Services Buyer will define their transportation capacity requirements by developing a forecast based on aggregated demand covering extended periods of time. (i.e. product/order forecasts are rolled up and extended to shipment forecasts). These requirements should take into consideration seasonality, promotions, production capacities, as well as other factors. As a shipping horizon gets closer, the transport capacity forecasts may become more detailed. The transportation capacity requirement message is sent to the Logistic Services Seller. |
| show | transport_instruction | Transport Execution | The main objectives of the Transport Instruction are to communicate and share the arrangements (through the agreed conditions) of the movement of the goods (including collection and delivery) between all parties involved and providing the information necessary to perform the handling of the goods.
The Transport Instruction will be sent by the Logistic Services Buyer (supplier, retailer, 3rd party warehouse or freight forwarder) to a Logistic Services Seller (freight forwarder or carrier) upon order creation.
The Transport Instruction can include a request for either executing a consignment or executing a shipment. The trading partners need the ability to differentiate between less detailed transport instructions (shipments) and more detailed instructions (consignments). |
| show | transport_instruction_common | Transport Execution | This package contains the components that are determined to be common to the Transport Instruction messages and helps to enforce consistency across them. |
| show | transport_instruction_response | Transport Execution | A Transport Instruction Response may be sent from Logistic Services Seller to Logistic Services Buyer in order to confirm the instruction and to provide further detail. Exchanging this message is optional. In many cases there exist standing agreements that the Logistic Services Seller will accept all Transport Instructions from the Logistic Services Buyer ‘as sent’. |
| show | transport_pickup_dropoff_common | Transport Execution | This package contains the components that are determined to be common to the Transport Pickup Dropoff messages and helps to enforce consistency across them. |
| show | transport_pickup_dropoff_confirmation | Transport Execution | This business message enables the confirmation for an appointment to collect goods at a pick-up location or to deliver goods at a drop-off location.
In the pick-up / drop-off confirmation besides the detailed time and location (dock door) additional handling instructions might be included. |
| show | transport_pickup_dropoff_request | Transport Execution | This business message enables the request for an appointment to collect goods at a pick-up location or to deliver goods at a drop-off location.
Initial information about the collection and delivery of goods may already have been exchanged in the transport instruction. However, the party where the goods are collected (consignor / pick-up location /shipper / ship-from location) or delivered (consignee / drop-off location / receiver / ship-to location) will not in all cases be aware of the transport instruction details or they might have changed.
In the pick-up / drop-off request the carrier can specify delays or other relevant status information that might impact the time of collection or the time of delivery. |
| show | transport_status_notification | Transport Execution | This scenario allows for the exchange of information regarding the status of transport execution progress at any point (in time or place) within the full transport chain.
A status message may be sent:
- as the result of a request or requests for information (through the Transport Status Request message) regarding a consignment or consignments;
- on a scheduled basis at predetermined times;
- on the occurrence of a selected event or events;
- on the occurrence of an exceptional event as agreed by the partners involved. |
| show | transport_status_request | Transport Execution | Message requesting information on the transport status and movements of a transport related object. |