Ceramics CRM
In ceramics two separate production batches of the same product differ in shade and calibre; when the square metres left short arrive later from a different batch, they do not match the floor already laid. That two dealers are separately tracking the same site also becomes clear only when the price comes to the table.
An order carries batch and calibre fields alongside the product code; which batch went to which project is read from the record, and a later shortfall request attaches to the same record.
- Record the order with batch and calibre fields, and read from the record which batch went to which project
- Link the project to the dealer who entered it first, so that the existing record appears in the list when the same site is entered a second time
- Attach the shade sample sent to the architect to a task together with the batch it came from, and drop the ones with no answer into a list
- Produce the quote with both the square metre and the box equivalent, and track the quantity sent to site and the quantity invoiced from the same line
| Batch and Calibre | An order is a record that carries batch and calibre fields alongside the product code; a later shortfall request attaches to the same record. |
|---|---|
| Project Record and Dealer | A project is a record and it is linked to the dealer who entered it first; when the same site is entered again the existing record appears in the list. |
| Shade Batch Sample | A shade sample sent to an architect or a dealer is a task; the batch it came from and its reply date sit in its fields, and the ones with no answer drop into a list by date. |
| Square Metres and Boxes | A quote line carries both the square metre and the box equivalent; the quantity shipped and the quantity invoiced are read from the same line. |
What is sold in ceramics is not just a product code: between different batches of the same code there is a difference in shade and calibre. The first shipment to a site comes out of a single batch, but when the thirty square metres left short during the work are asked for months later, that batch has run out and the goods that arrive do not match the floor already laid. A second difficulty comes up on the dealer side: two dealers ask for a price on the same project and both order from the same manufacturer; because it is not clear who brought the job in, the price is pushed down and the work leaves no profit for anyone. What became of the samples sent is never asked either.
In Rapitek CRM an order is a record that carries batch and calibre fields alongside the product code; how much went to which project from which batch is read from this record, and a shortfall request that comes later attaches to the same record. A project is a record and it is linked to the dealer who entered it first; when the same site is entered a second time the existing record appears in the list, so who is following it is clear before the price is discussed. A shade sample sent to an architect or a dealer is a task; the batch it came from and its reply date sit in its fields, and the ones with no answer drop into a list. Because square metres and the box equivalent are kept together on the quote line, the quantity sent to site and the quantity invoiced are read from the same place.
The scope of the plans and the separately priced items are set out on the pricing page.
