A batch call that "succeeded" with failures inside it
How you'll know: The batch returns 200, but a few products never changed. Each item in the response carries its own result, and failed ones have an error object instead of the updated record.
Fix: Read every item in the response, not the status code. Log the failures with their code and message and retry only those.
Asking for more than 100 per page
How you'll know: per_page=250 comes back as a 400 with rest_invalid_param.
Fix: Stay at 100 or below and page through. For very large pulls, combine that with modified_after so each run is small.
The host blocks you before WooCommerce does
How you'll know: Requests start returning 403, 429 or an HTML page from the host's firewall partway through a backfill. WooCommerce itself doesn't set a rate limit on the REST API, so this comes from the server.
Fix: Throttle requests, back off on failure, and run large backfills off-peak. If the host still blocks it, ask them to allowlist the integration's IP.
Reading errors as if they were all the same
How you'll know: Everything non-200 gets the same retry. The API returns JSON with code, message and data.status: 400 for a bad request, 401 for auth or permission, 404 for a missing resource, 500 for a server error.
Fix: Retry 500s and host throttling. Don't retry 400s and 401s, because the same request will fail the same way. A 401 on a key that used to work usually means its WordPress user was removed or lost permissions.
Custom data that seems to vanish
How you'll know: A field a plugin added at checkout isn't in the order's top-level fields.
Fix: Look in meta_data on the order and on each line item. That's where order numbers from other systems, custom product attributes and plugin fields end up.