Compliance responsibility

Before changing anything

Identify the system of record and capture the current state. A configuration must be tied to the correct account, SKU, store or order. Avoid changing several variables at the same time: doing so makes diagnosis harder and can hide the actual cause of an issue.

• Verify the account, store, SKU or order identifier.
• Confirm market, currency, payment status and destination when relevant.
• Keep the initial state before any material change.

Test on a narrow scope

When the topic affects an integration, order, publication or operating setting, run a controlled test first. Use one product, one order or one store whenever possible. Then verify the result in both systems involved instead of assuming that an on-screen success message means the change propagated everywhere.

• Define the expected result before testing.
• Check upstream and downstream statuses after the action.
• Scale the change only after a reproducible test.

Keep useful evidence

A clear history shortens resolution time. Keep identifiers, test time, useful screenshots, exact error messages and the observed result. For product or compliance questions, also retain the market, document version, batch or file used so that two different scopes are not compared by mistake.

• Date and time of the test.
• Relevant identifiers and statuses.
• Exact screenshot or error message when a mismatch appears.

When to contact support

Escalate when real behaviour differs from this guide, when an expected permission or data point is missing, when a status remains stuck after verification, or when an action could create a financial, regulatory or logistics effect that is difficult to reverse. Include the context and collected evidence so the team can reproduce the case.