Journal
Which add-to-bag events a fashion desk actually needs
Size, colour, and bundle lines each deserve their own bag event if merchandising is going to argue about last weekend.
A single “add_to_cart” event is enough if you only want to know that someone tapped. It is not enough if merchandising wants to know whether size M left the grid while XL sat. In apparel apps we see in Johor and the Klang Valley, the useful split is usually: simple SKU bag, bundle bag, and guest bag.
Guest bag matters because a large share of festive browsing never signs in. If guest bags vanish on login, Monday’s bag count and Friday’s order count will never meet.
Bundles (baju plus shawl, watch plus strap) should not inherit the parent’s identifier. That error makes bag counts look like a triumph and average order value look like a mystery.
We do not ask engineering for a dozen flavour events on day one. We ask for the three that the buying meeting already argues about. Extra events can wait until those three are trusted.