Preparing a catalog sample in Petaling Jaya
What to export before week one: identifiers, public titles, featured flags, and the pairs of listings that are the same app in two languages.
The sitting fails in the first week more often than in the last. Not because the map is hard, but because the extract is a screenshot folder with no dates.
If you are in Petaling Jaya or elsewhere in the Klang Valley and you already know you will ask for an assessment, prepare a table. One row per listing in the window. Columns we actually read: a stable identifier, the public title, category, first public date, publisher identifier, conversation count, completed-transfer date if any, and a yes/no for featured in that window.
Leave buyer names out. If your export cannot drop them, count conversations instead of forwarding the thread.
Mark bilingual pairs. A cleaning app titled “Home Clean PJ” and “Cuci Rumah PJ” is one stall if it is one publisher and one offer. If you do not mark the pair, we will count a crowd.
Say how featured slots are assigned, including the unofficial ones sold in a chat. A sample that pretends every featured flag is a public auction will misread the aisle.
Bring a person who can attend the working session with authority to rest a listing. A proxy who can only “take it back to the group” means you paid for a rehearsal.
Weekend spikes deserve a sentence in the intake note. A Saturday flood of home-repair listings after a storm is not the same depth as a Tuesday. We would rather shift the window than average the storm into the quiet week and call it liquidity.