> For the complete documentation index, see [llms.txt](https://docs.terminal.africa/tship/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terminal.africa/tship/miscallaneous/rate-card-pricing.md). # Rate Card Pricing The pricing object returned with a rate card holds the price matrix. This section describes that object. | Attribute | | Description | | -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | band\_surcharge\_overrides | *array* | Always empty on merchant endpoints. The per-band markup structure behind the prices is not exposed. | | currency | *enum* | Currency every price in the matrix is quoted in. | | currency\_symbol | *string* | Display symbol for the currency e.g. ₦. | | delivery | *object* | Price matrix for the delivery direction. See below. | | format | *enum* | How to read a price. Must be one of ***standard*** (the cell is the total price for a shipment in that band) or ***multiplier*** (the cell is the price per unit — multiply by the chargeable weight). | | includes\_surcharges | *boolean* | Always `true`. Prices are what you are charged, with all surcharges applied. | | name | *string* | Display name of the rate card. | | pickup | *object* | Price matrix for the pickup direction. See below. | | rate\_card\_id | *string* | Unique reference for the rate card. | | unit | *string* | Unit the weight bands are measured in. Usually ***kg***. | ### The matrix object `delivery` and `pickup` have the same shape. A card can price one direction only, in which case the other has `has_pricing` set to `false`. | Attribute | | Description | | ------------ | --------- | ----------------------------------------------------------------------------------------------- | | has\_pricing | *boolean* | Indicates the matrix holds at least one price. | | rows | *array* | The weight bands. See below. | | zones | *array* | The columns of the matrix. Each has a ***zone\_code***, a ***name*** and a display ***label***. | ### The row object | Attribute | | Description | | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------- | | band | *string* | The weight band as a range e.g. ***1-2***. | | cells | *object* | Prices for this band, keyed by ***zone\_code***. A value of `null` means the card has no price for that band and zone. | | label | *string* | The band's upper bound, for display as the row heading. | | override\_range | *string* | Marks a band priced outside the card's standard surcharge set. `null` on a normal row. | {% hint style="info" %} The columns of a rate card **are** its zones, so a price matrix is unreadable without knowing which countries fall into each one. Use the zones download to get that. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.terminal.africa/tship/miscallaneous/rate-card-pricing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.