Set up net payment terms on a BigCommerce store's customer group using the Customer Groups and Orders API

Steps

1. Identify or create the target customer group: GET /v2/customer_groups or POST /v2/customer_groups with {name: 'Net30 Wholesale', is_default: false, discount_rules: []}.
2. BigCommerce does not natively enforce net-day payment due dates at the platform level for non-B2B Edition stores — implement net terms via the order's payment_status and a custom due date stored in a custom_field or the order's staff_notes.
3. When an order is placed by a group member, listen for the store/order/created webhook; the payload includes the customer_id and customer_group_id.
4. On receiving the webhook, update the order with PUT /v2/orders/{order_id}: set payment_status to 'Awaiting Payment' and compute the due date (orderDate + 30 days), storing it in custom_fields or an external system.
5. Build a cron job or scheduled task that queries GET /v2/orders?customer_group_id={id}&payment_status=Awaiting+Payment and flags any orders where your stored due date has passed without a payment_status change to 'Paid'.
6. For full net-terms lifecycle management (credit limits, statement generation) on BigCommerce, use BigCommerce B2B Edition's built-in payment terms (covered in the B2B Edition API route) rather than building it manually.