Cosmetics Retail Merchandising & Store Execution Software for Malaysian Business

Each chain and format has its own picture-of-success: a department store beauty hall flagship gets a multi-zone brand corner with tester arrangement, GWP display, and brand-owned counter design, a specialty beauty chain gets a simpler open shelf layout, a smaller satellite gets a single shelf check. The BA and merchandiser app loads the right check at each counter, and reports roll up by chain and format.

Brand corners are configured as separate installation tasks with start and end dates, agreed location in the beauty hall, and installation photo requirements. BAs and merchandisers capture installation, mid-window check, and dismantle photos. AI image recognition verifies signage, tester arrangement, and SKU presence. Exception flags fire when installation does not happen, when the counter gets displaced by competitor, or when tester units go missing.

The AI model is trained on the brand's SKU library plus chain-specific counter templates. It handles partial occlusion, reflective glass surfaces, varied lighting in beauty halls, angle variance, and mixed-SKU arrangements. For confidence-flagged photos, the system routes to a human reviewer rather than auto-passing. Model retraining cycles incorporate new SKU launches and seasonal POSM variants without long downtime.

The KAM walks into JBP with a chain-specific scorecard: counter look compliance, brand corner setup status, end-cap occupancy, GWP display fulfilment, share-of-shelf vs competitor, and execution score against the agreed picture-of-success. The data is photo-backed and timestamped. When a chain claims credit for execution that did not actually happen, the platform shows the evidence.

Festive rollouts are scheduled campaigns with chain-specific store lists, POSM kits, installation windows, dismantle dates, and picture-of-success references. The BA and merchandiser app shows the rollout plan per counter. Installation status updates in real time. Exception reports flag counters where festive POSM is not up or has been dismantled early. Trade marketing sees the rollout heatmap during the season.

GWP displays are configured as separate installation tasks with start and end dates, agreed location, agreed product mix, and agreed POSM elements. BAs capture installation, mid-window check, and dismantle photos. Exception flags fire when installation does not happen, when GWP gets pilfered, or when display is rearranged off-brief. Trade marketing and finance see actual realisation against the GWP investment.

Tester stock-out events are logged at the SKU and counter level by the BA during the shift. The platform classifies the cause (depleted by shopper sampling, missing or pilfered, replacement delayed). Daily tester availability dashboards by chain and category let the KAM raise the issue with the chain immediately rather than waiting for the next JBP cycle, especially during seasonal launches.

Counter photos go through AI for both own-brand SKU detection and competitor SKU detection. Share-of-shelf is calculated as facings per brand relative to category total. Reports show share-of-shelf trends per chain, per region, per category, and per counter. Brand teams see where competitor expansion is happening before it shows up in chain sell-out reports.

Trade marketing sees campaign rollout status, POSM deployment rate, audit pass rate, and corrective action closure. KAMs see chain-wise compliance scorecards ready for JBP. Brand leadership sees national execution score, chain-wise breakdown, competitor share-of-shelf trends, and brand corner installation tracker. Drill-downs go from country to chain to counter to individual visit photo.

The mobile app is offline-first. Inside department store basements and dense beauty halls where mobile reception drops, BAs and merchandisers capture photos, complete the audit checklist, log out-of-stock SKUs, and submit the visit. Once signal returns at street level or at the front of the store, all data uploads to the cloud. Conflict-handling prevents duplicate visits if a sync happens after a manual entry.