When you create a webhook you can include a headers object, and BigCommerce sends those headers with every callback. Use it to add a shared secret or basic auth, and reject any request without it. Payloads only carry IDs, and you fetch the details with your own token, so a forged call can't feed you fake order data. It can still make you do work, which is why the check matters.
Custom fields on products and orders are the other thing to plan for. Decide early how each one maps into your ERP or accounting system, because that mapping is what breaks when the catalog changes. See BigCommerce integrations for common targets like NetSuite, and B2B Edition if you sell wholesale, since its API has its own base URL and needs an X-Store-Hash header.
n-frames builds and runs BigCommerce API syncs for stores that would rather not own this: webhooks with a scheduled backstop, calls paced to the plan's quota, and custom fields mapped to the system on the other end. Inventory is a common one to sync first.