Summary
Highlights
The meeting begins with a discussion on ongoing fixes and the development of a new membership module. This module will integrate with the cashback point system and partner contacts, aiming to streamline membership management which was previously complex between Omni and Odoo. The goal is to move membership management entirely into a dedicated Odoo module due to multi-channel complexities.
The speaker outlines their current tasks, including finalising coupon fixes and deploying Odoo adjustments for the POS module. The main focus is on initialising the new membership module, which will serve as the core for profile cards and membership. This module will track purchase points and cashback points, centralising all related logic. Another key component is the 'point move' feature, which will function as a journal tracking system for points.
The team discusses prioritizing tasks for immediate deployment. Mas Per is assigned to create a prototype UI for the profile card, with design specifications provided. This UI development is crucial for integrating the Alnus Club feature, which will combine different club functionalities into a single profile card. The prototype will be deployed to staging first.
A task involves hiding the old membership card interface on both desktop and mobile, replacing it with the new UI prototype. Following the UI prototype completion, the next step is to define the API contract for the profile card and membership between the backend and frontend. This ensures that the frontend and backend development are aligned, with the API contract serving as a baseline for future Odoo API development.
The discussion shifts to existing tasks, specifically the migration of price lists. It is decided to put these tasks on hold, including B2B price lists, as per previous feedback. The team also addresses an issue regarding returned packaging not appearing correctly in the system, particularly for items purchased through different channels. This highlights potential discrepancies in partner input or transaction recording.
Mas Perdi raises a concern about customers purchasing items at a physical 'zero' location and attempting to return packaging via the website. In some cases, only certain items (e.g., rice packaging) appear in the return list, while others (e.g., softener packaging) are missing. This suggests potential issues with how transactions or partner data are logged, either through incorrect manual input or duplicate partner entries, which can lead to customer accounts not being properly linked to their purchases.