Josh Wall (Unlicensed) reviewed the output from the October call:

• GTIN adoption and implementation is the preferred end state
• Distributor participation is viewed as critical to success
• A cross-reference table is not intended to recreate or build a parallel AGIIS Product Directory

Review high-level solution

Josh Wall (Unlicensed) reviewed the proposed (currently) solution:

Q: What is the limit on the cross reference table? Identifier-specific: MFR product to any provided identifier (distributor, retailer)

Q: Are we moving away from GTIN? No; the agreed upon goal is still to get to GTIN. It's to continue to try and adopt and implement GTIN while supporting messaging improvements with the reality of product identification as it is today.

Observe that product is associated with the party being dealt with, which is problematic for the down-channel partner. Agreed that this is the problem scenario; intent is to address the reality of that, while offering a consistent format and single spot for such cross references to be shared.

Also observe that there are so many ways/places to create a product record that would need to touch the GTIN/MFR product identifier/channel partner product identifier. Agreed; noted that, further, the cross reference or association will need to be managed by the retailer or their service provider.

Josh Wall (Unlicensed) opened the floor for input and discussion. End question is whether distributors are willing to participate in a requirements discussion.

Q: Will there be a GTIN for each package size? Could be, depending upon how you want to enumerate your products. 

Friz Schuster observes that Homologa provides this service in France. Is there interest in working together on this?  Observe that AgGateway has a preference to bring conversations together and not pick winners. That conversation may go beyond where we are today. Do appreciate that there are other conversations going on about connecting different resources when it comes to reference data.

Julie Benick supports communication on the matter. Kay Campe concurs; observes that we need to keep this as simple as possible and consider access/authorization. Greg Fish is open to the conversation; scope is a consideration. Other distributors are in general support.

Data Elements and Availability

• UOM needs? Seems to be a value
  • Conversion? Selling, reporting, what are we talking about here? 
  • Observes that UOM can get dangerous; noting that MFR, DST and RET may all use a different one. Observe that the statement may need to be that retailer is responsible for managing but something needs to be included.
  • Observe that UOM code lists are at issue - ANSI vs UN-REC-20, for example.
  • Noted that the AEC project implemented based on single UOM for messaging. Is ordering UOM different than reporting UOM? Yes. Could you have multiple cross references? Not necessarily, but would likely be more than one UOM per product record.
  • Clarification on retailer as consumer of the records. Although it is an interesting question on whether the retailer returns their cross references for review and comment. Robust discussion. 
• Will there be links for regulatory data? Not envisioned for this file per se. That data can be referenced in other resources.
• Will the effort justify the value in the event we really do get to the GTIN as a common identifier? Maybe, but note that we've been talking about moving there for a looooong time. Will this be used as an excuse not to get to the GTIN?
• Discussion about level of effort to implement GTIN. Observation that GTIN isn't "spoken" in terms of the crop protection products. That will be a discussion needed at the business level. Focus is still on seed when it comes to item/product management. Barcoding brings value for the GTIN. Needs to be a game-changer; can't just be an identifier swap.
• Observation that in other regions, Europe especially, there is a compliance driver to implement GTIN. 
• Discussion on EAN/GTIN-13 vs GTIN-14. 

Support for an additional meet up with a straw model to look at, along with a process flow that supports the cross reference model.

• Tory Bjorklund willing to be part of that discussion 

Timing? Can we pull this off in December? Look at second week of December for an open date. Member Services will be sending on an email announcement soon.