Footwear CRM
In footwear an order is not a quantity but a size run: while size 38 of a model sells out, size 44 waits on the shelf, and the dealer only wants the size that is moving. When pre-orders are written on paper and in-season demand is taken over the phone, how many pairs of which size go into production is decided by guesswork.
An order line carries a model and a size field; a model's size spread is read from those lines. In Rapitek CRM a warranty case opens with a defect type and recurring defects gather in a list.
What we set up, and how
- Record dealer pre-orders with a model and size run breakdown and look at the production plan from the same list
- Record in-season demand as a separate type from the pre-order and see in the report which size sells out early
- Open warranty and return cases with a defect type; have the resolution note written on the case, so later cases opened with the same defect type are read from those records
- Tie subcontracting workshop work to a task with its deadline date, and have the person taking delivery sign on the signature screen in the mobile app
| Size Run | An order line carries a model and a size field; a model's size distribution and the difference from dealer to dealer are read from those lines. |
|---|---|
| Pre-Order and In-Season Demand | Both are order records linked to the same account; the type is separated in a field, and the season report is split in two by that field. |
| Warranty Case and Defect Type | A warranty case is a record; the model, the defect type and the decision given are its fields. The resolution note is written on the case, and later cases opened with the same defect type are read from those records. |
| Subcontracting Workshop Deadline | Work given to a workshop is a task; the deadline date and the quantity are its fields, and as the deadline approaches the task moves up the list. |
In the footwear business two separate calendars run at once: the collection pre-order is collected months before the season, while in-season demand comes only for the models that are working and only in certain sizes. When the pre-order is on paper, in-season demand on the phone and warranty complaints such as a sole coming away in a separate ledger, which model is really selling and which model is coming back are never seen side by side.
Rapitek CRM keeps the dealer as an account record; the pre-order and in-season demand accumulate under the same account with a model and size breakdown. Because the warranty case is a separate record, which defect recurs on which model is read from the history; the resolution note is written on the case, and later cases opened with the same defect type are read from those records. Because work given to a subcontracting workshop is tracked as a task, jobs whose deadline is approaching drop into the list by themselves.
The scope of the plans and the items priced separately are set out on the pricing page.
