Choose fields that affect purchases
Compare service identifier, action, rate basis, minimum, maximum, and relevant descriptive conditions where the API supplies them. A catalog refresh is more than a price update. Some important terms may require reviewing documentation outside the response.
Classify the change
Distinguish a simple text correction from a change that affects customer approval or order eligibility. A higher minimum, different action, or removed listing should trigger a review of the corresponding product. Preserve the previous values for open-order context.
Apply changes deliberately
Update new purchasing decisions only after the mapping and displayed scope agree. Keep already accepted orders linked to their original records. Do not rewrite historical charges or descriptions merely because the latest catalog response is different.
Decision checklist
| Decision | What to check |
|---|---|
| Fields | Purchase-relevant attributes |
| Change | Cosmetic or material |
| History | Prior order context preserved |
Worked example
A hypothetical catalog refresh changes a service minimum from 100 to 1,000. Updating only its price leaves a storefront that still accepts invalid 200-unit requests. The quantity rule and visible offer must be reviewed together.
Example figures explain the decision; they are not current prices or promised results.