The Global Language of Business
GS1 logo
  1. Home
  2. Standards
  3. Traceability
  4. Discover TraceWay
  5. TraceWay

Navigate GS1 TraceWay

Consult GS1 TraceWay to learn about the three phases of a traceability implementation project - diagnosis, design and deployment. Within the tool, you can explore the essential steps that include, their respective outputs and detailed information such as applicable GS1 standards, actions to be performed, benefits, tips or resources to achieve each output.

 

  • Select a phase or the pre-requisites - corresponding steps appear

  • Select a step: related outputs appear below. The first output is selected by default. Detailed information for each output is outlined on the right

  • To switch from phase, step or output, just click where you want to go

 

Traceability Project Setting

Defining and approving the traceability project business case before the project starts.

GS1 standards

Not applicable.

Actions
  • Document the company's reasons for wanting to implement or improve traceability (objectives, drivers or problems they want to solve such as meeting a new legal requirement, improving inventory management, managing risks in procurements, fighting counterfeiting, enabling transparency with consumers, reducing waste, etc.).
  • Capture any specific requirement or expected benefit of the future traceability system that is already known (e.g., granularity, speed, interoperability, automation).
Tips

By measuring the collateral short-term benefits for GS1 Standards adoption (e.g., purchasing - contingency sourcing, logistics - better truckload optimization, supply and demand planning - more accurate forecasting, improved inventory management), organisations can engage and involve other departments that could provide support in terms of resouces and budget for the project. In the absence of early involvement and showcasing short-term successes across various areas, sustainaing a long-term effort might become challenging. GS1 MOs can provide valuable assistance by sharing insights through case studies to shed light on these aspects.

Resources
  • GS1 GTC Checklist: all or some of the 12 sections of GTC Control Points could be considered as critical success criteria by the company.
  • GTS2 section (3.3.4 for example) on performance criteria (e.g., speed, data quality).
GS1 standards

Not applicable.

Actions

Define what's in and out of scope of the project with regards to the following aspects at minimum:

  • Locations (facilities of the company).
  • Internal processes (across all sites, facilities and head office).
  • Items (products and their logistic formats, assets).
  • Trading partners (they could be all or a subset of raw material suppliers or customers. They may be defined by items in scope).
GS1 standards

Not applicable.

Actions

Define the staff required for the project: identify the project manager, the departments and Subject Matter Experts that need to participate (e.g., IT, Logistics, Supply Chain, Quality, Safety, Production, Legal Affairs, Sustainability) or staff that should be informed (e.g., Marketing).

Tips
  • IT resources and internal systems/data sets will be needed or impacted. Involving IT resources depending on the level of integration from the beginning is a guarantee to success.
  • Promote the traceability project from the very beginning so the entire company is aligned and resources are allocated for this effort in all departments as needed.
GS1 standards

Not applicable.

Actions

Capture the constraints applicable to the project derived through discussions with each Subject Matter Experts from the project team (e.g., budget, regulations/policies, technology, human resources, organisation & user impact such as not to compromise day-to-day business).

GS1 standards

All GS1 standards applicable for traceability.

Actions

Assess the company's preparedness for traceability best practices by evaluating its maturity level in information technologies, GS1 membership status and the possession of certificates indicating traceability or record keeping capabilities (e.g., HACCP or GFSI recognised food safety certificates in food, ISO Chain of Custody standard).

Tips
  • Assessing this at an early stage will help determine how big the gaps may be, define a realistic plan, and start to advance some foundations if necessary such as establishing GS1 membership.
  • Gather existing reference material and best practices for traceability in preparation of the project e.g.,
    • GTS2.
    • GTC checklist.
    • EPCIS/CBV 2.0 Implemention Guide.
    • Sector specific application standards for identification and traceability (implementation guidelines).
    • Non GS1 documents per sector e.g., ISO, GFSI, GDST.
    • Applicable international and domestic regulations (e.g., EU Food Law, EU Product Passport, US FDA).
Resources

To check GS1 membership status:

  • GEPIR.
  • Verified by GS1 (best in 2023 with GLN Registry).
  • Refer company to appropriate GS1 local office to pursue membership.
Benefits

Researching existing best practices and applicable standards at an early stage will make it easier to proceed with the next steps.

GS1 standards

Not applicable.

Actions

Provide a comprehensive cost estimation for the project (e.g., man hours, technology acquisition, consumables, quantity of resources needed).

GS1 standards

Not applicable.

Actions

Define a step by step intial Project Plan. The plan must include a time schedule or Gantt Chart for all activities.

GS1 standards

Not applicable.

Actions

Consolidate all the defined project details into a document know as the Business Case for the traceability project, which will require approval from company leaders.

Diagnosis

Establishing current traceability capabilities and gaps within the organisation.

Tips

GS1 GTC Checklist is a key tool to perform assessments. Some GS1 Member Organisations (MOs) provide traceability assessment services. Assessing current traceability capabilities and gaps may be a stand alone activity. Yet when performed in preparation for implementing a new traceability system, documenting all the learnings (not only the gaps) will help speed up the design phase.

GS1 standards

GS1 General Specifications for the definition of parties, and locations.

GS1 GTC Checklist.

Actions
  • Determine and summarise parties in scope of the traceability project (internal and external), their roles in the supply chain and locations. e.g., identify plants, warehouses, distribution centers, third party cold storage facilities, etc.
  • Qualify and document identification keys currently assigned or captured by the company (including proprietary keys if any).
  • Qualify and document which data they manage for each key (master data) and how they do it.
  • Document gaps that have been identified.
GS1 standards
  • GTS2 for the definition of traceable items and logistic hierarchies, and corresponding identification keys.
  • GS1 General Specifications for identification of items.
  • GTC Checklist.
Actions
  • List traceable items (e.g., trade items, assets, logistic units).
  • Determine the traceable items hierarchies.

For all traceable items:

  • Qualify and document product type (e.g., ingredients, materials, Product in Process, finished product).
  • Identify and document their level/type of packaging (e.g., Consumer unit, Pack with consumer units, Carton with consumer units, Pallet with cartons (LU), Super Bags (LU), others).
  • Qualify and document the keys currently assigned by the company.
  • Determine their level of identification:
    • class level (e.g., GTIN, SKU).
    • lot/batch level.
    • instance level (serial).
  • Document gaps that have been identified.
GS1 standards
  • GS1 General Specifications for barcoding and labelling.
  • GS1 AIDC application standards.
  • GS1 standard for EPC RIFD tags (EPC/RFID Tag Data Standard).
Actions
  • Review the physical identification and data carriers used by the company (barcoding, labelling, RFID Tags) to identify Traceable Items.
  • Determine if they support requirements from customers and regulations and if there are specific marking requirements for data carriers such as linear, 2D and RFID, e.g., healthcare, fisheries, fresh foods, etc.
  • Document gaps that have been identified.
GS1 standards

Not applicable.

Actions
  • Assess whether the company has a diagram documenting the flow of traceable items (products, assets, trade items and their logistic units) from receipt of materials and ingredients to the dispatch of finished products. This should include information about business processes, parties and locations, traceable items and documents involved (Dispatch Advice, Purchase Order, Transport Order, etc.).
  • Document gaps that have been identified.
GS1 standards

GS1 traceability application standards (implementation guidelines) if defining minimum CTEs.

Actions
  • Describe how products move from inputs to customers, i.e. all the business processes and activities involved in the traceable items flow in scope of the project, and how these internal processes are linked with each other. E.g.,:
    • Receiving: Inputs.
    • Material Warehousing: Inputs, storage, outputs (supply to production).
    • Production: Input, use, outputs.
    • Products in Process and Finished Products: Warehousing: inputs, storage, picking.
    • Dispatch: outputs.
  • Document gaps that have been identified.
Tips

CBV 2.0 Business Steps values provide examples of activities.

GS1 standards

GS1 traceability application standards (implementation guidelines) if defining minimum KDEs.

Actions
  • Evaluate the data management approach employed by the company for each traceable item (e.g., dates, weight, units, and other requirements from customers and regulations) and review for presence in respective master data.
  • Document gaps that have been identified.
GS1 standards

Not applicable.

Actions
  • Comprehend and record all the application systems, hardware and technologies that are currently used to control processes related to traceability.
    e.g., Enterprise Resource Planning (ERP), Warehouse Management System (WMS), Transport Management System (TMS), Excel, Handhelds, etc.
  • Document gaps that have been identified.
GS1 standards

Not applicable.

Actions
  • For every traceable item, identify the software systems functions, capabilities and documents (paper forms) that support the business processes, e.g., rules and formulas (software functions) on how data is generated, exchanged and captured to support traceability related business processes.
  • Identify the retention duration.
  • Document gaps that have been identified.
GS1 standards
  • Applicable GS1 data dictionaries and data sharing standards (to be specified for EDI, EPCIS, Digital Link and 2D.
  • GS1 sector specific application standards for traceability when specifying minimum data to be exchanged or best practices for data sharing of Trace Request.
Actions
  • Assess the current traceability requirements and needs for traceability information from customers and suppliers.
  • Document current data exchanges for traceability between the company and its trading partners:
    • all types of data: master, transactional and visibility data.
    • Data collected, recorded and shared.
    • Data sharing method and interoperability.
  • Document the gaps that have been identified.
GS1 standards
  • Applicable GS1 data dictionaries and data sharing standards (to be specified with GS1 EDI and EPCIS SMEs) including Digital Link and 2D.
  • GS1 sector specific application standards for traceability when specifying minimum data to be exchanged or best practices for data sharing.
Actions
  • Document the important internal reporting capabilities that can be used by staff for traceability requests (e.g., a report available by GTIN showing current inventory and product on order - especially product in route, in the event of a recall; inventory expiry analysis to show raw materials and finished goods that are expired or nearing expiration).
  • Assess the process for external trace requests.
  • Document the gaps that have been identified.
GS1 standards

Not applicable.

Actions
  • Determine all the current procedures affected by traceability requirements (because it gives information on how they currently perform traceability and these may need to be modified after the design of the traceability system) e.g.,:
    • SOPs (Standard Operational Procedures).
    • Traceability Procedure.
    • Food Safety Procedure.
    • Recall Procedure.
  • Document gaps that have been identified.
GS1 standards

Not applicable.

Actions
  • Determine if the company currently has a traceability team or individual(s) responsible for traceability (taking into account work-shifts).
  • Specify internal staff and roles related to all the activities mentioned in this diagnosis phase.
  • Document gaps that have been identified.
GS1 standards

Not applicable.

Actions
  • Establish if there are traceability trainings implemented for the staff.
  • Document gaps that have been identified.
GS1 standards

Not applicable.

Actions
  • Review if the company currently has a monitoring and maintenance plan to analyse and correct the performances of the traceability system and potential problems (Traceability System Assessment, Continuous Improvement, Corrective and Preventative Actions (CAPA). The plan may include:
    • Tracebility operational monitoring.
    • Traceability performance criteria.
    • Traceability audits.
    • Traceability maintenance plan.
  • Document gaps that have been identified.
Tips

ISO 9001 for Quality Management Systems may be used.

GS1 standards

Not applicable.

Actions

Produce a Traceability Diagnosis Report capturing all the learnings from the diagnosis phase, including the gaps assessment (ref. GS1 GTC Assessment Report).

Design

Defining a traceability system that fulfills the initial objectives and addresses the identified gaps.

Tips

The level of traceability capability should be in proportion to the value and risk profile of the product, or as mandated by regulations. Integration of the relevant GS1 standards will enable interoperability with other systems.

GS1 standards

Not applicable.

Actions
  • Identify the gaps directly related to the objectives of the company.
  • Check the feasibility to solve these gaps.
  • If feasible, confirm the project objectives, scope and plan and ensure agreement on the gaps that will be solved.
  • If not feasible, agree on prioirising gaps that need to be solved. Then review and adjust the initial objectives, and/or revise scope and plan accordingly.
Tips
  • This step remains live throughout the design phase.
  • Initiate this step with a review of the Phase 1 Diagnosis and Traceability Gaps report.
  • Take a realistic approach to timelines: develop and/or refine a project plan (Gantt) and identify the critical path to project completion.
Benefits

Align team on objectives and scope.

GS1 standards
  • GS1 identification key for parties and locations (GLN).
  • GS1 GLN Data Model.
Actions
  • For each party listed in the previous phase (Step 1.2), determine locations that should be identified in the traceability system.
  • Define how gaps identified in the previous phase will be solved in terms of identification keys for parties and locations (e.g., assigning GLNs).
  • Ensure all the necessary data for traceability will be described in master data records. Master Data for traceability purposes should include for example: identification keys (GLN or other), name, address, phone, contact details, GPS for some locations.
Tips
  • Include physical locations such as plants, warehouses and distribution centers.
  • Ensure master data comes from one source of truth.
  • GLN is essential for the use of EPCIS and recommended for EDI.
Resources
Benefits

Unambiguous identification enables interoperability and to trace back to the parties involved.

GS1 standards

Not applicable (see identification keys).

Actions
  • Document the traceable item types listed in Step 1.2 (items received, created/modified and delivered - inputs, creation, outputs - across the processes in scope of the traceability project).
  • Document item hierarchies and describe if these are e.g., Ingredients, Materials, Product in Process (PP), Finished Products (FP), Logistic Units (LU) and Consumer Unit, Pack with consumer units, Carton with consumer units, Pallet with Cartons (LU), Super Bags (LU), others.
Tips
  • The configuration of the item being traded needs to be considered to describe the item hierarchies.
  • Unidentified item hierarchies cannot be controlled or measured.
Resources
Benefits

Identification of traceability items and their hierarchies is critical to designating the right level of granularity for traceability.

GS1 standards

GS1 Identification keys for products (GTIN), logistic units (SSCC), assets (GRAI, GIAI), consignments (GINC) and shipments (GSIN).

Actions
  • Determine identification levels needed:
    • class level (e.g., GTIN, SKU).
    • batch/lot level.
    • instance level (individual item with a unique serialised number).
  • Determine which identification keys should be assigned (e.g., GTIN, GTIN+batch/lot, GTIN+Serial Number).
Tips
  • The identification level of the traceable items received or shipped (e.g., pallet individually identified with an SSCC) is not necessarily the same as the identification level of the items traded, ordered or invoiced by each trading partner (e.g., cartons).
  • To find the right level of identification, consider the precision needed to meet the business objectives, the potential impact in terms of costs, and the value and risks associated with the product.
  • All items moving between partners should be identified with a standard identification key to avoid re-labelling and loss of traceability.
Resources
Benefits
  • The granularity of identification determines how precise the traceability system will be.
  • Use of GS1 identifiers increases the reliability and decreases the collective cost of traceability systems.
GS1 standards
  • GS1 Global Data Synchronisation Network (GDSN).
  • GS1 Global Data Model.
Actions

Ensure all the necessary master data for traceability is available in the master data records e.g., short description, long description, dimensions, weight, type of packaging, corresponding logistic units ("parents & children"), and other master data depending on the traceability objectives (including applicable customer and legal requirements).

Tips

Ensure master data originates from a single source of truth.

Resources
Benefits

Accuracy and completeness of master data is fundamental for the effectiveness of the traceability system.

GS1 standards

GS1 standards for barcodes and EPC/RFID (such as EAN/UPC, ITF-14, GS1 DataBar, GS1-128, GS1 DataMatrix, GS1 QR code and GS1 Digital Link, GS1 Logistic label, EPC Tag Data Standard).

Actions

For each traceability item, specify the physical identification and data carriers to be used taking into account:

  • the type of physical identification (e.g. label and/or RFID tag, direct part mark, swivel tag) considering product specific constraints (e.g. item washed and reused many times).
  • applicable standards and needs for interoperability.
  • additional data elements for identification (e.g. dates, weight, units) and applicable Application Identifiers (AI).
  • information that should be human readable and ready for automatic data capture.
  • customers and legal requirements.
  • sector specific best practices.
Tips
  • All items moving between partners should have a standard data carrier to avoid re-labelling and loss of traceability.
  • GS1 Digital Link helps barcodes and other data carriers become web links.
  • The GS1.org website has a wealth of information on globally-standardised data carriers.
Resources
Benefits
  • Connect the physical flow with the information flow.
  • Use of GS1 data carriers for physical identification is essential for interoperability.
GS1 standards

Not applicable.

Actions
  • Produce a physical flow diagram, or complete a pre-existing one from Phase 1 Step 1.3.
  • Document the flow of traceable items (products, assets, any trade items and their logistic units) from receiving to despatch.
Tips

Include information about business processes, parties and locations, traceable items and documents involved (e.g., Dispatch Advice, Purchase Order, Transport Order, etc.).

Resources

External business process mapping tools such as Bizagi or Visio. Microsoft PowerPoint may also be used to develop a business process map.

Benefits
  • A visual representation of the physical flows helps identify events that should be CTEs, where we need software and hardware, and to identify the gaps.
  • It also allows to explain the system to others (executive management or people who require training).
GS1 standards

EPCIS Core Business Vocabulary (CBV) 2.0, business steps values.

Actions

Determine which business steps are Critical Tracking Events and identify their type of CTE.
For example, the following business processes and steps are typical CTEs (when applicable):

  • Receiving: Inputs (Transportation CTE).
  • Material Warehousing: Inputs, storage, outputs (supply to production) (Transportation CTE).
  • Production: Inputs, use, outputs (Transformation CTE).
  • Products in Process and Finished Products Warehousing: inputs, storage, picking (Transportation CTE), palletising (Transformation CTE-Aggregation).
  • Despatch: outputs (Transportation CTE).
  • Disposal (Depletion CTE).
Tips
  • Identify which CTEs are required for internal traceability to meet the organisation specific objectives vs. those for external traceability with trading partners.
  • Any transformation, receiving and dispatching activity should always be a CTE.
Resources
Benefits
  • Determining the CTE types enables correct determination of appropriate KDEs in step 2.5.
  • If one or more CTEs are not identified there is a good chance that all CTEs will NOT be properly linked.
GS1 standards

Not applicable.

Actions

Define the physical actions that will have to be performed for each CTE as part of the business process e.g.,

  1. Receiving:
    • Take sample and wait for quality approval.
    • Capture label with handheld and register transaction.
    • Enter products to Warehouse.
  2. Processing:
    • Consume input materials and relate to the output product lot (as per the Work Order).
    • Print label with barcode for products, cases and pallets.
    • Capture label with handheld and register pallets creation.
  3. Shipping/dispatch:
    • Read pallet label and control against transport order.
    • Load pallet on the truck.
    • Distribute to customer and check delivery.
Tips

Combine the activity of performing this step with Step 2.5 "KDEs to record at each CTE".

All traceable items should be physically identified when created.

Resources
Benefits

This is the starting point for defining material/softwares and writing the procedures.

GS1 standards

GS1 data dictionnaries and data models (such as GDM and GDSN for product master data, EPCIS for event data).

Actions

For each CTE, specify KDEs to be recorded considering the type of event (including links between inputs and outputs for transformation and aggregation events), objectives of the company and existing best practices or sector-specific application standard.

Tips
  • KDEs are easier to identify if this step is performed in conjunction with Step 2.4, "Define CTEs in the physical flow".
  • Applying GS1 standard data models (or data attributes) to structure the recorded KDEs will enable the company to be more prepared to share some of this data with trading partners.
  • The association of the identification keys of the traceable item (e.g., GTIN, GTIN+lot, SSCC ) together with the CTE and any documents related to the event and/or item (e.g., a certificate of analysis, or other certificates, claims or credentials) are to be recorded to ensure links between the physical and information flow are maintained.
Resources
Benefits
  • It is critical to record a set of KDEs per CTE that enables minimally viable traceability.
  • KDEs impact the precision (depending on links management between inputs and outputs) and the depth of the traceability system (how much information will be available).
GS1 standards

GS1 Global Document Type Identifier (GDTI).

Actions
  • For each CTE and their related KDEs, define the record keeping method such as: software (e.g., ERP, WMS, TMW, Traceability Software, Blockchain system) and software function (e.g., MIGO transaction in SAP to transfer material), document used (e.g., excel sheet, paper, word), and hardware used (e.g., handheld, scanner, RFID portal/gateway, printer, PC terminal).
  • Ensure that each document and software function transaction/form will be assigned an identification key (e.g., the Work Order or Purchase Order number generated by a software, or alternatively a GDTI).
  • Determine the retention duration.
Tips
  • Try to reduce the number of systems/softwares/documents involved in every CTE to reduce complexity and optimise efficiency of trace requests.
  • Solutions for record keeping may be existing, require enhancement or be entirely new.
  • Regulations within an industry sector may define record retention duration.
Resources

GS1 General Specifications for document identification using the GDTI.

Benefits
  • This step may help identify and communicate the gaps in traceability software and systems.
  • Well defined record keeping methods make it easier to write and apply the procedures. It actually determines which procedures will be involved.
GS1 standards

Not applicable.

Actions
  • Review/decide if a verification method is needed to validate the accuracy of the recorded data.
  • If applicable (if yes), define the verification method.
Tips

Mass balance may also contribute to verifying the information recorded (by checking data consistency).

Resources
  • Verified by GS1 for checking GTINs accuracy from suppliers (max 30 public queries per day or to be discussed with MO).
  • GEPIR for checking GLNs from trading partners.
Benefits

Industry regulations may require companies to verify that records are accurate.

GS1 standards

Not applicable.

Actions

Document the important internal reporting capabilities that will be available for the staff and record how this information should be obtained for internal or external trace requests.

Tips
  • For reports that will frequently occur, it is adviseable to utilise software and automation to minimise the use of resources (labour).
  • Reporting capabilities include not only data but also documents that may be required or shared with others (taking into account what regulations stipulate).
Benefits
  • The reporting capabilities' quality can provide insights to management and identify areas where opportunities and improvements can be made.
  • Those in charge of performing the trace requests will be able to follow a step by step procedure to collect information from different sources (it may not be just a case of "push this button").
GS1 standards

GS1 data dictionaries, data models and data sharing standards (such as GDD, GDM, GS1 XML, EANCOM, EPCIS and EPCIS/CBV, GDSN, GS1 Digital Link).

Actions
  • Define the traceability data that will need to be received and shared with customers and suppliers, whether systematically or on request. It may include sharing data with final consumers or patients or trading partners that are not direct partners.
  • For each source or recipient of traceability data, define the type(s) of technology(s) expected to be used (e.g., EDI, email with excel sheet, data pools, blockchain, webpage) and the actual data sharing solution that the company would like to use (e.g., a software or solution shared with one or more trading partners).
  • Determine how data will be represented by referencing GS1 data dictionaries, data models and data sharing standards.
Tips
  • Data to share is typically a sub-set of the data the company records.
  • Organising data sharing with trading partners may be addressed as a separate project.
Resources
Benefits

Data sharing technologies will benefit from the use of GS1 standards for interoperability and data quality.

GS1 standards

Not applicable.

Actions
  • Define requirements that need to be provided to suppliers and information to customers when implementing traceability.
  • Anticipate potential issues (e.g. feasibility) or impact on relationships with suppliers and customers and how to manage these.
Tips
  • Information gathered from Industry groups, industry initiatives or GS1 sector specific guidelines can help specify each stakeholder's needs.
  • Establishing formal requirements requires trading partner collaboration, therebye building trust.
Benefits
  • Have visibility on which trading partners will be prepared.
  • be ready when potential issues araise with trading partners.
GS1 standards

Not applicable.

Actions
  • Identify the procedures that will be impacted and require modification (or must be created) when implementing the new traceability system.
  • Typical procedures impacted by traceability are: Production, Quality, Food Safety, Recall and SOPs in general (Standard Operational Procedures) for business operations from receipt of raw materials to shipping.
Tips
  • Using the physical flow diagram drafted in the previous step can help.
  • It is a best practice to ensure that every CTE and its related actions are captured within a procedure (existing or new).
Benefits
  • Establishing procedures is critical to an effective traceability system.
  • Procedures make it possible to identify areas of improvement.
GS1 standards

Not applicable.

Actions

Define the responsibilities, expertise and skills required for the staff in charge of managing and using the traceability system once implemented. This may include representatives from various departments such as Quality, Logistics, Engineering, Labeling, Procurement, Customer Service and Legal.

Tips
  • Consider current and future state.
  • There should be a responsible person for all tasks, including for the overall traceability system.
Benefits

Responsible staff need to be identified in order for procedures to be effectively followed.

GS1 standards

Not applicable.

Actions

Define the training material that should be developed when implementing the traceability system in order to train the traceability team and the staff involved in the impacted procedures.

Tips
  • Train staff on What they have to do,Why and the consequences if they don't perform their activities correctly.
  • Ensure the company's leadership is aware of the traceability solution, what it does and does not do, and how it supports their staff in their roles.
Benefits

Training staff to correctly apply the procedures is critical to an effective traceability system.

GS1 standards

Not applicable.

Actions

Establish how the company will measure the traceability system once implemented. It may include:

  • traceability system performance criteria.
  • tracebility operational monitoring.
  • traceability audits.
  • traceability maintenance plan.
Tips
  • Regulations, customer and internal requirements may describe or mandate performance criteria.
  • GS1 GTC Checklist is one of the tools to monitor the traceability system. It is ideally applied after implementation to verify gaps have been filled and objectives have been met.
Resources
  • All or some of the 12 sections of GTC Control Points could be considered as critical success criteria.
  • GTS2 section 3.3.4 on performance criteria (e.g., speed, data quality), The GS1 Global Traceability Standard.
  • ISO 9001 Quality Management Systems provides KPIs and how to define them.
Benefits

A reliable monitoring system ensures the value of the investment in traceability over the long-term.

GS1 standards

Not applicable.

Actions
  • Establish the project CAPEX and OPEX. CAPEX is capital expenditure and OPEX is Operating Expenditure.
  • E.g. for CAPEX: Hardware to buy (purchase), software, licences, configuration, interfaces development, consulting, training, additional staff (they may also be a reduction).
    E.g., for OPEX: supplies, maintenance (such as errors that may happen), operations continuity (have internet all the time, maintenance of all equipment related, staff dedicated to supervise maintenance, hosting, etc.).
  • Estimate the savings/benefits, e.g.,
    • Savings due to time reduction in data entry.
    • Savings in inventory costs (increased turnover, reduced shrinkage, reduced inventory, etc.).
    • Potential savings in administrative overhead reduction.
    • Potential improvement in visibility (expected increase in productivity).
    • Expected savings in supply chain support costs (improved coordination and reconciliation of deliveries).
    • Reduction of accidents.
    • Reduced transport costs (reduced waiting times).
    • Reduced cost for recalls/recall exercises/audits.
  • Estimate ROI of the Traceability Project.
Tips
  • Ensure the company's finance leaders are directly involved in this step.
  • The design of the traceability system may be reviewed in order to fit the financial resources of the company (iterations with the above steps). The financial aspects may also lead to phasing the implementation.
Resources

Online ROI calculators and guides.

Benefits

Even if there is no clear quantified ROI, it is recommended to fully understand the costs and recurring costs of the traceability system.

GS1 standards

Not applicable.

Actions

Produce the traceability system design report including a draft implementation plan.

Tips
  • All the outputs of the design phase along with cost estimates are to be included in the report.
  • Use the Diagnosis Report from Phase 1 as the basis for the Phase 2 report to minimise the effort.
Benefits

The design report provides company leadership with the needed information to make go/no-go decisions on the investment.

Deployment

Implementing and controlling the designed traceability system.

Tips

This may need a phased approach. Applicable GS1 standards and resources are similar to the design phase.

GS1 standards

Not applicable.

Actions

Produce the final implementation plan including:

  • roll out and training timelines.
  • potentially testing /pilots (may include data validation).
GS1 standards

Not applicable.

Actions
  • Perform testing/pilots (may include a roll out and training for a small part of the traceability process).
  • Analyse results of testing/pilots.
  • Revise the traceability system design report and implementation plan based on the outputs of the testing/pilots.
GS1 standards
  • GS1 identification key for parties and locations (GLN).
  • GS1 GLN Data Model.
Actions
  • Assign keys to parties and locations defined.
  • Describe all necessary master data for traceability in the master data record (ref. steps 2.2).
Resources
GS1 standards
  • GS1 Identification keys (ref. 2.3).
  • GS1 Global Data Synchronisation Network (GDSN).
  • GS1 Global Data Model.
  • GS1 standards for barcodes and EPC/RFID (ref. 2.3).
Actions
  • Acquaint the company with GS1 (if it is not yet acquainted).
  • If the company is creating or processing traceable items (manufacturers, retailer that is re-packaging, has a distribution platform, transforming products in the shop, etc.):
    • Assign keys to traceable items as previously defined (e.g., GTIN, GTIN+lot or serial number, SSCC).
    • Design labels/RFID tags to be printed with all the required information including selected data carriers (and/or RFID tags), GS1 Application Identifiers (and/or EPC Code).
  • Describe all the necessary master data for traceability in the master data record (ref. steps 2.3).
Resources

See step 2.3.

GS1 standards
  • GS1 data dictionaries, data models.
  • GS1 data sharing standards (ref. 2.6).
Actions

Implement the selected new software, hardware and solutions. Ensure they integrate the applicable standards for interoperability.

Tips

Plan purchasing, delivery and implementation times. This could require defining a RFP (Request for Proposals), a tender process, a selection period and a BBP (Business Blueprint) preparation before implementing.

Resources
GS1 standards
  • GS1 data dictionnaries and data models.
  • GS1 GDTI (ref 2.5).
Actions
  • Complete the documents and/or software/ hardware functions with KDEs that are not currently being registered.
  • Develop the non existing documents and/or software/hardware functions that needs to be added to record and monitor/control the traceability process and its KDEs.
  • Implement the verification method if planned in design phase.
Resources
GS1 standards

Not applicable.

Actions

For each CTE defined, establish the processess and the actions that need to be performed according to what was defined in the design phase and the use of the software/hardware/solution implemented.

Resources
GS1 standards

Not applicable.

Actions
  • Implement all the requirements to share traceability information with suppliers and customers.
  • Communicate information about the traceability requirements to Trading Partners.
GS1 standards

Not applicable.

Actions

Develop/complete and document the procedures identified in the previous phase in order to support the new traceability capabilities.

GS1 standards

Not applicable.

Actions

Identify and establish the internal "traceability team" (people with roles and responsibilities related to the traceability system that are usually from various departments).

GS1 standards

Not applicable.

Actions

Develop the traceability training material.

GS1 standards

Not applicable.

Actions

Deliver a traceability training program to staff defined in previous phase.

GS1 standards

Not applicable.

Actions
  • Go live with the new traceability system with newly designed capabilities.
  • Promote the benefits of the new traceability capabilities within the company (e.g., the marketing department can promote the launch of the new system and highlight the importance of traceability as part of the value of the product).
Tips

This "post implementation" promotion can provide a more tangible measurement of the benefits of the traceability system (from a certain group or category of products for example).

GS1 standards

Not applicable.

Actions

Monitor, maintain, review and analyse the performance of the traceability processes to identify successes and problems (Traceability System Assesment, Continuous Improvement, Corrective and Preventative Actions (CAPA)).

GS1 standards

Not applicable.

Actions

Go-live executed. Monitoring, maintaining and continuous improvement.

FAQs about GS1 TraceWay

GS1 TraceWay was developed by traceability experts within the GS1 community. Their insights draw from extensive experience gained over many years and a wide array of implementation projects spanning various sectors worldwide.

GS1 TraceWay assumes that the choice of technologies and tools should be left to each individual organisation. It offers a practical approach for organisations to define the solution that best fits their needs. The integration of GS1 standards facilitates the capability to seamlessly connect with trading partner solutions.

GS1 TraceWay is the best and most comprehensive methodology recommended to utilising and adopting GS1 standards for traceability. Its added value extends beyond the use of GS1 systems, encompassing common business and regulatory traceability requirements.

Within GS1 TraceWay, you’ll discover a comprehensive mapping between the core elements of traceability systems and the key GS1 standards. For explanations about these GS1 standards and how to apply them, materials about each specific GS1 standard or standard area (e.g., GS1 barcodes) should be consulted and can be accessed on the GS1 website.

GS1 TraceWay’s design centres around individual company traceability projects and their interactions within their specific supply chains. When considering collective industry initiatives, certain steps or outputs might not directly apply. In such cases, a simplified methodology tailored to industry-wide effort could prove more suitable.

A recommended starting point is to review the GS1 TraceWay Overview. This will help familiarise you with the phases, steps and related outputs. You have the flexibility to delve into any phase or step of your interest within GS1 TraceWay as needed. Whether for addressing current concerns, gaining insights into upcoming tasks, or reviewing completed actions, you’re free to navigate the material based on your requirements.

Although the steps are outlined in order, certain steps can be performed at the same time.

GS1 TraceWay can be used in any sector or by any type of industry or company, whatever their role within the supply chain.

GS1 TRACEWAY – DISCLAIMER & PERMISSION TO USE
Disclaimer

GS1 TraceWay is a traceability tool that refers to the use/implementation of standards developed and administered by GS1 AISBL ("GS1"). GS1, under its GS1 Intellectual Property Policy ("IP Policy), seeks to avoid uncertainty regarding intellectual property claims. The IP Policy requires that participants in the GS1 Work Group that developed the GS1 standards referenced in TraceWay agree to grant a royalty-free licence or a reasonable and non-discriminatory (RAND) licence to permit implementation of the standard, as those terms are defined in the IP Policy.

Please note that an implementation of one or more features of standards referenced in TraceWay (whether GS1 standards or other standards) may be the subject of a patent or other intellectual property ("IP") right that is not covered by the licence granted under the IP Policy, and any such patent or other IP right is not subject to the licencing obligations of GS1. Moreover, the agreement to grant licences provided under the IP Policy does not include IP rights and any claims of third parties who were not participants in the corresponding standard-development Work Group.

Accordingly, GS1 recommends that any organisation developing an implementation designed to be in conformance with the standards referenced in TraceWay (whether GS1 standards or other standards) should determine whether there are any patents that may encompass a specific implementation that the organisation is developing and whether a licence under a patent or other intellectual property right is needed. Such a determination of a need for licencing should be made in view of the details of the specific system designed by the organisation in consultation with their own patent counsel.

TRACEWAY IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF THIS TRACEABILITY TOOL, ITS METHODOLOGY OR ANY OF THE GS1 STANDARDS REFERENCED IN IT. GS1 disclaims all liability for any damages arising from use or misuse of TraceWay, whether special, indirect, consequential, or compensatory damages, and including liability for infringement of any intellectual property rights, relating to use of information in or reliance upon TraceWay.

GS1 retains the right to make changes to TraceWay at any time, without notice. GS1 makes no warranty for the use of TraceWay and assumes no responsibility for any errors which may appear in TraceWay, nor does it make a commitment to update the information contained herein.

GS1 and the GS1 logo are registered trademarks of GS1 AISBL.

Permissions

Copyright © 2023 GS1 AISBL

This work has been developed by GS1 AISBL with the contribution and assistance of GS1 Member Organisations. It is licensed to non-GS1 organisations under a CC BY-NC-SA license