Fashion CRM
In a fashion brand the work is tied to the season calendar: the week the collection is shown to the buyer, the window in which orders are taken and the delivery date to the store chase one another. When that calendar sits in a diary and store and online channel sales sit in separate spreadsheets, whether a style really took off or came back is only understood once the season has closed.
A season is a record; the showing, order-taking and delivery dates are its fields. A return record carries a style and a channel field, and the breakdown is read from those two.
- Set the collection season up with calendar steps, so that a task drops to the person responsible as the showing, order-taking and delivery dates approach
- Send the lookbook and collection showing to the buyer from the shared inbox and read the WhatsApp and SMS correspondence on the same card
- Keep store and online channels separate on the account record and see which channel a style is working in during the season
- Total return records by style and channel field and base the next collection's decisions on that difference
| Season Calendar | Every collection season is a record; the showing, order-taking and delivery dates are its fields, and a step whose date is approaching drops into the task list of the person responsible. |
|---|---|
| Collection Showing Despatch | The lookbook link that goes to the buyer goes out from the shared inbox; the WhatsApp and SMS correspondence sits in the same flow on the buyer's card. |
| Channel Separation | Store and online sales are separated by the channel field on the account record; the same style's sales in the two channels are totalled separately according to that field. |
| Return Difference by Style | A return record carries a style and a channel field; which style comes back more often through the online channel is read from the breakdown of those two fields. |
In a fashion brand a season is not a date but a chain: the week the collection is shown to the buyer, the window in which the order is taken and the delivery date to the store are all tied together. When that chain sits in a diary, the buyer correspondence on a phone and store and online sales in separate spreadsheets, a step slipping is only noticed once the next step goes wrong.
Rapitek CRM keeps the season on its own record with its dates; from the showing through to delivery, every step drops into the task list of the person responsible. WhatsApp and SMS correspondence with the buyer accumulates on the same card; because the store and online channels are separated on the account record, which channel a style is working in and which channel it is coming back from is visible before the season closes.
The scope of the plans and the items priced separately are set out on the pricing page.
