Meeting minutes 2017-07-05 Tesco UK
Date
July 5, 2017
Attendees
- Danail Deltchev (Unlicensed)
- Alena Brezinova
- Beatris Bunova
- Graham Broughton
- Tesco team
Goals
- Expectation setting – Jordan will brief what is Tesco’s ambition for the first phase of work and what the main focus for the next 3 – 4 months
- A quick demo/walkthrough of what is Pentagon’s offering in this space
- Go through API integration and on-boarding process in Tesco – API’s, Schema, Data model(s) etc
- Go through what is needed from functional perceptive - Go through registration process, on boarding process, product induction process, order management process, finance invoice process etc
- Discuss what are current pain points in each of the above processes and how we can resolve some of the issues and build right backlog for enhancements
Discussion items
Item | Who | Notes |
---|---|---|
General | Tesco/Pentagon | • Pentagon supports integration with both API and FTP. We have confirmed that Tesco integration with Pentagon will only focus on API and not FTP. However, the integration from Suppliers and/or Sellers should provide integration with API as well as FTP and allow supplier and seller to choose what is best fit for their needs |
Gap analysis / Considerations | Tesco | Tesco went through Pentagon solution/bridge and noted the following considerations |
• There is currently no Account Management/Tesco admin account function to be able to restrict and monitor Partner Accounts • There is currently no performance and KPI monitoring available in the Pentagon solution • Customised reporting is a real benefit to Marketplace • The UI and product data management is clean and looks really good • Pentagon can potentially load balance feeds coming in through the Tesco API • Deleted SKU’s can be archived so they are still available if needed for reference • Pentagon can provide a managed service which covers training, customer support, on boarding support, content work • Pentagon happy to take responsibility to push good content into Tesco and work with the Partner on this • Tiles and views on the dashboard are great, and can be customised to show required info to Partners • Import and Export functions are available. We need to ask whether this allows offline data entry for products and then import this back into Pentagon • Pentagon has manual process to work with TAM to fix and reprocess any failure transactions • Pentagon does not have success metrics reports as of now. But could be built if data is made available • Need to understand and work through the process to commutate stores returns to Pentagon against an order - There is no solution in place to provide this information to integrators at the moment • How we automate data model at both the ends • 365 day rule in Tesco – we need to think about how we remove this | | Potential requirements that we need to go through for phase1 rollout | Tesco/Pentagon | • Listing management including suspend and delete. Suspend would need to send suspend + 0 Stock + remove SKU from future inventory feeds, until it comes back into stock • Discontinue – would send a delete call into Tesco and archive SKU • Need Partial refund to prompt contact to TAM for subsequent refunds • Reason codes need work to map against existing Pentagon codes if applicable, or Pentagon can use the Tesco mapping • Click & Collect functionality needs to be considered • Return to store to be considered where we can make info available to Pentagon once initiated within Tesco • Listing against existing products – need to allow for this and potentially send Listing + Image feeds first and if listed then no need to add product data (Assuming content is good!) • GTIN checker top provide back product information/images etc. • Improve Returns to store • Automate Data model at both ends • Provide NFRs for scaling requirements - Lorraine agreed to provide these details to Ben Malcolm |
Action items
-
[ ] Tesco team to set individual workshops to go over the following topics:
Go through each API interface in details and understand any gaps and mitigations Focus on deriving Click and Collect solution part of the integration Listing engagement and Inventory functionality - how Pentagon would handle inventory, suspensions, price changes Throttling, load balancing, error Handling and retry mechanism Need to access the risk around PIM accepting one amendment feed and how this can be mitigated via Pentagon Inventory updates - understand if we could have a more flexible API call to avoid limited call that we currently Derive operations process for all the limitations in Phase1