Describe the unit before the rate
A rate card should state exactly what is being priced. “Per item” can mean a physical unit, an order line, a distinct SKU, or a handling action. Those terms are not interchangeable. The agreement should define the measurement in language both operations and finance can use.
Include the customer, warehouse, relevant service, effective period, currency, and exclusions. A clear scope prevents the same activity from being accidentally priced by two exclusive rules.
Make allowances and thresholds explicit
Document whether an allowance resets per order, day, customer, warehouse, or month. Specify whether a threshold applies to all volume or only the portion within a band. If multiple services contribute to a minimum, name them.
Store examples at the boundaries. For a 500-order allowance, examples at 499, 500, and 501 orders reveal interpretations that a paragraph of prose can leave ambiguous. Examples should support the agreement rather than replace it.
Keep amendments reviewable
Create a new draft version when terms change. Retain the active version while the draft is reviewed. Show effective dates and identify any example whose expected outcome changes.
Replay the proposed terms over a representative historical period using the same activity. If source records also changed, separate that effect from pricing. Preserve old terms with closed periods so a later amendment does not rewrite their explanation.