What problem does it solve? Loggro ERP uses a flat data model where every size/color combination is an independent item, while One Star uses a hierarchical model of parent products with variants. This Skill defines the architecture and rules for reconciling these two models so catalog synchronization does not create duplicate products or overwrite curated store content. ## Core Features & Use Cases - SKU Prefix Grouping: Splits Loggro SKUs at the first hyphen (e.g., CAM01-M-ROJ) to group variants under a parent product with slug CAM01. - Safe Upsert Rules: Synchronization updates price, unit of measure, variant stock, and erpId while never overwriting images, enriched descriptions, web categories, or banner positions. - Adapter-Based Architecture: All Loggro access goes through the loggro.adapter.ts adapter behind the generic IERPAdapter interface, keeping business logic decoupled from the ERP client. - Use Case: When a developer modifies the product sync flow in erp-sync.service.ts, this Skill ensures they follow the grouping rules and never import LoggroClient directly into business logic. ## Quick Start Review the Loggro ERP integration rules and refactor the product synchronization service so all ERP access goes through the IERPAdapter interface.
