Order translations

An order status translation is the name of one of the store's own (custom) statuses in another store language, addressed by the id that List order statuses returns. Customers see it on the order confirmation, order status and account pages in that language, and staff who use Tringify in that language see it in the order list and order details; without one, everyone sees the status's own name. System statuses (Pending payment, Processing, Completed, Cancelled) are worded by Tringify in every language and refuse translations with ORDER_STATUS_TRANSLATION_SYSTEM. Only name is translatable; it follows the rules of a status name (not blank, at most the order statuses limit's name_max_length characters, no control characters). A translation written against an earlier name is reported outdated. Store Admin, the Tringify mobile app, standard AI Translator jobs, translation CSV (resource order_status) and MCP translate the same names. Each change sends order_statuses/translations/update, or order_statuses/translations/delete when a translation is cleared. Returns a resources entry keyed by order_status:{id} for each requested status (at most 100 per call); a status without a translation has an empty object. Fields without a translation in this locale are omitted from the response. An omitted field is not empty: shoppers see the store's base-language value, which the resource's own GET endpoint returns.

An order status translation is the name of one of the store's own (custom) statuses in another store language, addressed by the id that List order statuses returns. Customers see it on the order confirmation, order status and account pages in that language, and staff who use Tringify in that language see it in the order list and order details; without one, everyone sees the status's own name. System statuses (Pending payment, Processing, Completed, Cancelled) are worded by Tringify in every language and refuse translations with ORDER_STATUS_TRANSLATION_SYSTEM. Only name is translatable; it follows the rules of a status name (not blank, at most the order statuses limit's name_max_length characters, no control characters). A translation written against an earlier name is reported outdated. Store Admin, the Tringify mobile app, standard AI Translator jobs, translation CSV (resource order_status) and MCP translate the same names. Each change sends order_statuses/translations/update, or order_statuses/translations/delete when a translation is cleared. Each row is one order status in one language: id, locale (any enabled non-default store locale) and fields. Rows for several languages can be mixed in one call; send at most 100 rows (one row = one order status in one locale) and at most one row per order status and locale. Each row is saved on its own: a failing row never stops the others. Empty values clear the matching field translation; omitted fields keep their translation. Every row is validated exactly like the single translation endpoint. The response has totals (rows, saved, failed) and one results entry per row in request order: {id, locale, status} with status saved or failed. A failed row carries the full error (code, message, details); its codes are the single endpoint's codes plus TRANSLATION_ROW_DUPLICATE. A saved rich-text row whose unsafe markup was removed lists warnings. A top-level code and message give the outcome: TRANSLATIONS_SAVED (200, every row saved), TRANSLATIONS_PARTIALLY_SAVED (200, success: true; the message counts saved and failed rows and names the failure reasons, e.g. "2 saved, 1 failed. No source text found for the requested fields (description).") TRANSLATIONS_NOT_SAVED_RETRY (503 with a Retry-After header, success: false; no row saved because every row failed only with TRANSLATION_WRITE_BUSY, so the same call can be sent again after error.details.retry_after_seconds) or TRANSLATIONS_NOT_SAVED (422, success: false; no row saved and at least one row failed for another reason). Both carry the same totals and results in error.details. With an Idempotency-Key, repeating the same request re-applies nothing that already saved and retries the failed rows. A write waits at most 2 seconds for other translation writes of the same item or of a clashing name or slug (for example a translation CSV import writing the same language); writes of other items, types and languages never wait. A row or call that fails with TRANSLATION_WRITE_BUSY (HTTP 503) saved nothing: send it again after error.details.retry_after_seconds (the call's Retry-After header says the same). Every row or call either saved or reports an error; none is left in an unknown state.

An order status translation is the name of one of the store's own (custom) statuses in another store language, addressed by the id that List order statuses returns. Customers see it on the order confirmation, order status and account pages in that language, and staff who use Tringify in that language see it in the order list and order details; without one, everyone sees the status's own name. System statuses (Pending payment, Processing, Completed, Cancelled) are worded by Tringify in every language and refuse translations with ORDER_STATUS_TRANSLATION_SYSTEM. Only name is translatable; it follows the rules of a status name (not blank, at most the order statuses limit's name_max_length characters, no control characters). A translation written against an earlier name is reported outdated. Store Admin, the Tringify mobile app, standard AI Translator jobs, translation CSV (resource order_status) and MCP translate the same names. Each change sends order_statuses/translations/update, or order_statuses/translations/delete when a translation is cleared. Returns the stored name translation in the selected locale with is_outdated; a status without a translation in this locale returns an empty fields object. Fields without a translation in this locale are omitted from the response. An omitted field is not empty: shoppers see the store's base-language value, which the resource's own GET endpoint returns.

An order status translation is the name of one of the store's own (custom) statuses in another store language, addressed by the id that List order statuses returns. Customers see it on the order confirmation, order status and account pages in that language, and staff who use Tringify in that language see it in the order list and order details; without one, everyone sees the status's own name. System statuses (Pending payment, Processing, Completed, Cancelled) are worded by Tringify in every language and refuse translations with ORDER_STATUS_TRANSLATION_SYSTEM. Only name is translatable; it follows the rules of a status name (not blank, at most the order statuses limit's name_max_length characters, no control characters). A translation written against an earlier name is reported outdated. Store Admin, the Tringify mobile app, standard AI Translator jobs, translation CSV (resource order_status) and MCP translate the same names. Each change sends order_statuses/translations/update, or order_statuses/translations/delete when a translation is cleared. Send an empty string to clear the translation; readers in that language then see the status's own name. A write waits at most 2 seconds for other translation writes of the same item or of a clashing name or slug (for example a translation CSV import writing the same language); writes of other items, types and languages never wait. A row or call that fails with TRANSLATION_WRITE_BUSY (HTTP 503) saved nothing: send it again after error.details.retry_after_seconds (the call's Retry-After header says the same). Every row or call either saved or reports an error; none is left in an unknown state.