Demo storefront on commercetools and a pick-and-pack mock-up
Pat has been proving an end-to-end solution to surface any unforeseen gaps.
The demo storefront. A demo website is connected to commercetools. It pulls mock product data with store-based pricing and inventory, switches stores with price and inventory guarding, searches products through commercetools, and runs cart and checkout (payment excluded). It is hosted on Vercel; the link is on the storefront item.
The pick-and-pack app. The incumbent pick-and-pack app was explored over the weekend and its core features reverse-engineered. A mock-up has been ported into both a web app and a mobile app, connected to the Experience API.
Next steps for a basic end-to-end workflow
Section titled “Next steps for a basic end-to-end workflow”- Hosting: publish the draft Experience API to the Azure sandbox (the Experience API in the sandbox).
- Store master: identify whether an existing solution can be used or a new one is needed, with DW (store and location master design).
- Staff access management: complete the design and the security review, with DW (staff access management).
- Store pick device enrolment: complete the design and the security team review, with Henri (store pick device enrolment).
- Mobile app lifecycle management: the baseline Android version is set; define the rollout and update path, with Henri (mobile app lifecycle management).
- OMS scope: complete the design and review (order engine design).
- commercetools order integration: design, review and standardise across all systems, covering real-time processing and reconciliation (order engine design and step 4).
- Online invoice integration: adopt the new flow the Market Retail team is building and align on the delivery timeline, with Brendan (order history and invoice design).
- Geo-polygon mapping and delivery boundaries: define the scope, the data stored and the process, with Henri (geo-polygon delivery boundaries).
- Payment integration: set up and configure CyberSource with commercetools (payment adapter to CyberSource).
Four of these (staff access, device enrolment, app lifecycle, delivery boundaries) were outside scope v0.6; Sean accepted them into Part 3 the same day.