Appearance
Carrier Enterprise
- salesforce
- add to cart
- Bundled products complete (ET
Baker/ECM
- stabilizing ordin environment (ETA day-to-day) CHALLENGE: ???
- frontend reskinning and boilerplate planning
- WIP on full stack integration for ECM And Baker
- reviewing approaches to manage the frontend (Adrian with bundling vs Pablo with forking)
- override methodology is still a WIP - Decision needs to be made
- working through the shopware tasks on the SXSW board with the rest of the teams
- reorganizing tasks into product restrictions etc.
Shopware Eric L
- finalizing architectural decisions
Homans/Latam
- waiting on NextJS frontend and domain
- gap analysis and development starting for those BUs
Gemaire
- production nextjs and graphql for productionn
Peirce
- add Mike O with Eric and Melissa
Domain
- pricing and inventory this week
- cart and checkout operations moved over (full purchase workflow)
Discussion
Branch Restrictions
- Ryan: are there synergies with what was being built by conduit
- Mike D: there is a flat file that blower leverages for pushing restrictions into Magento for cart rules
- Cleo: PIM has the zip restrictions
- TODO: get with the conduit team to understand how restrictions could be put in place
- QUESTION: is this related to delivery address; should this happen in checkout on before checkout
- NOTE: peirce also hides pricing/inventory based on location
4 restrictions
- brand and location (selling charter)
- customer attribute + product attribute (epa, licenses, training, customer brand)
- customer attribute + product attribute + location (CE NE Charter enforcement)
- product attribute (restricting flex sales)
What is the source of truth for charter restrictions at the different BUs?
Hide/Show is not the same as view price, Add to Cart/Checkout restrictions