Review supplier retry, rejection and content settings
Open **Orders → Supplier APIs** and edit the intended connection. Driver settings vary; review the description beside each control. You need supplier-edit permission and a clear understanding of the supplier’s duplicate-order and rejection behavior.
Processing controls
**Batch Processing** determines how many orders are submitted simultaneously in a bulk workflow. **Maximum Order Retry Attempts** controls retry behavior. Higher retry activity can increase duplicate-submission risk when the remote outcome is uncertain; do not raise it as a substitute for reconciling supplier orders.
**Do not auto reject order on API Error** keeps affected work available for manual review when communication fails. **Do not auto reject order** also prevents automatic rejection on a supplier rejection response. Enabling these settings creates a staff follow-up responsibility; it does not turn a failed supplier job into success.
Content and balance
**Auto fetch description from API** and **Auto fetch short info from API** can update the corresponding service content. Use them only when supplier text is appropriate for your customers. Review imported requirements and language after a catalog refresh.
**Low Balance Threshold** is used for the supplier-balance alert workflow. Confirm the account currency and alert destination before relying on it. A balance alert is not a real-time guarantee that every new order can be purchased.
**Expected result:** the connection’s saved settings match your operational process. Reopen it after saving and check a representative service. If existing work is already stuck, inspect its status and supplier reference separately rather than assuming a new default repaired the old order.