Tax

Every tax zone with its country, region and postcode criteria decoded, its priority, and the rates hanging off it. A zone is never returned without its rates, because a jurisdiction with no rate charges nothing. Rate percentages are decimal strings so figures like 25.5 reach the cents intact.

Create a tax zone and its rates in one call. A name is required, and every rate needs a percentage. An empty criterion list matches everything, so a zone with no countries is the fallback zone. States are matched by ISO 3166-2 code or by name for the countries that publish a list, so "Colorado", "CO" and "US-CO" all match the same address.

Change a zone's fields. Sending rates replaces the zone's whole set of rates and gives them new ids, so return each rate's translations unchanged if you want the overrides to survive. Omitting rates leaves them standing.

Delete a tax zone and its rates. Orders already placed keep the tax they were charged, because an order line carries its own snapshot.

Create a tax zone and rate for each EU member state at its standard VAT rate, and report how many were actually added. Idempotent by zone name, so calling it twice does not duplicate a jurisdiction and the count is what was added rather than what was offered.

Every tax engine an add-on registered, the store-level default engine code, whether the built-in zone and rate editors still govern anything, and the registered tax-id validators. KahunaCart ships no driver of its own, so engines is empty on a stock install and the connectors are add-ons; administration.state is full, partial or none, and none means the zone, class and rate routes answer 409.

Attach a registered tax engine to one tax zone, so a store can quote a connector for one jurisdiction and its own rates for another from the same install. Send an empty engine to unbind. The store-level default every unbound zone falls back to is the tax.engine setting rather than anything this tool writes.

Whether prices contain tax, per region and per currency, plus the published resolution order and the store-wide tax.included at the bottom of it. A store selling to the UK and the US needs both answers at once, which one boolean cannot express.

Say that one region or one currency is priced inclusive or exclusive of tax. attribute is region (the value is a tax zone id) or currency (the value is an ISO 4217 code). One answer per region per currency; creating a second for the same key is refused with 409.

Change a preference's scope or its answer. Omitted fields are left standing.

Remove a preference. The scope it covered falls back to the next level of the resolution order — the currency preference, then tax.included.

Import the 10-column rate table — country_code, state_code, postcode, city, rate, tax_rate_name, priority, compound, shipping, tax_class — as a csv string. Rows sharing a geography become one zone carrying several rates, which is what makes GST plus QST expressible. Idempotent on country, state, postcode, city, tax class and priority, so importing the same file twice updates rather than duplicates. A malformed row fails alone and comes back in errors with its line number.