Ecommerce integration

Connect BigCommerce service earnings to contractor pay

BigCommerce runs your store. Wingspan manages worker records and pay. Seller, affiliate, and service fees link store sales to contractor work. Your team checks the amount owed before payment. Orders and buyer profiles add context. They do not become workers or payables on their own.

BigCommerce logo BigCommerce
Wingspan

Connect the work to the payment

  • BigCommerce

    Orders and selected service fees

    Wingspan

    Payables

  • BigCommerce

    Order refunds

    Wingspan

    Payables

  • BigCommerce

    Order transactions

    Wingspan

    Payment status and references

Choose which records sync and when they move. Your team stays in control of work review and payment approval.

Link service fees to worker pay

Store orders link to agreed seller, affiliate, or service fees. Your team reviews each amount owed. Approved work or known fees create contractor payables. Finance approves payment before a pay run sends money.

Match store records to workers

BigCommerce store records and shared IDs link selected sellers, affiliates, and service workers to Wingspan worker records. Store buyers keep their own records.

Match wholesale sales with worker pay

Wholesale orders link receipts to client invoices. Your team checks related work and worker bills. Client billing and worker pay keep separate terms and approvals.

How BigCommerce works with Wingspan

BigCommerce runs online stores, orders, and buyer payments. Wingspan manages worker records, required checks, and pay. A worker record is a payee. It holds the selected Contractor or W-2 type.

Seller, affiliate, and service fees connect store sales to contractor work. Agreed terms set each fee. Store shoppers stay buyer records. A shipped order alone does not create a worker or an amount owed.

An engagement is a shared work template. An assignment is one worker's job under that template. It holds agreed rates and dates. Service work links to work items and logs. Managers review the work log. Approval creates one amount owed. The contractor sees an invoice. Your team sees the same amount as a payable. Finance approves payment in a separate step.

Known fees also support direct payables. Use one path for each amount owed. W-2 workers use pay statements and employee payroll runs with tax withholding. They stay out of contractor bills.

Wholesale orders link to client billing. Buyer money and worker pay stay separate. Shared order IDs and pay status return to BigCommerce.

Start with the records you already use

Order
Tracks store sales and items. It shows when orders ship.
Customer
Stores buyer contact details. It tracks buyer groups.
Order Transaction
Tracks customer card charges. It shows settled funds.
Order Refund
Tracks returned funds. It updates item totals.
Order Shipment
Tracks sent packages. It shows tracking numbers.
Customer Attribute custom field
Stores custom tags on buyers. Selected partner records hold shared worker IDs.
Order Metafield custom field
Stores custom data on orders. It holds Wingspan bill IDs.
B2B Company in B2B Edition
Holds business accounts. It tracks client terms and buyers.

Sync options

Choose which tool holds each record. Set the changes that sync between them. Connect your records to the Wingspan workflows below.

Orders and selected service fees

Payables

BigCommerce to Wingspan

Store orders add context to agreed seller, affiliate, or service fees. Known fees sync to contractor payables in Wingspan. Finance reviews the amount and approves payment. The order value does not itself set worker pay.

Order refunds

Payables

BigCommerce to Wingspan

Store refunds flag linked worker bills for review. Your team checks the work and agreed fee terms. Finance reviews any change before payment approval. A refund does not itself deduct funds from a worker.

Order transactions

Payment status and references

BigCommerce to Wingspan

Order transactions show buyer payment status. Shared IDs match receipts to client invoices. Your team uses the status when reviewing linked work fees. Buyer payments stay separate from worker pay.

Partner customer attributes

Workers

In both directions

Selected partner records hold a shared Wingspan worker ID. The ID links the partner to a worker record. That record keeps the chosen Contractor or W-2 type. Store shoppers stay buyer records.

Order shipments

Work logs and work items

BigCommerce to Wingspan

Shipment details give context for selected service work. Work items group into the linked worker job's work log. Managers review the log. Approval creates an invoice the payer sees as a payable. Finance approves payment in a separate step.

B2B companies

Client invoices and payers

BigCommerce to Wingspan

Selected B2B companies link to paying clients in Wingspan. Wholesale billing follows the agreed client terms. Client invoices stay separate from contractor payables.

Order metafields

Payables

Wingspan to BigCommerce

Wingspan bill IDs sync to BigCommerce order fields so your team can match each order to the related worker bill.

Integration workflows

01

Service work to contractor pay

A shipment links to a completed service job.

A store shipment links to completed service work. The work syncs to the contractor's work log in Wingspan. Agreed rates set the amount. A manager reviews and approves the log. Approval creates one amount owed. The worker sees an invoice. The payer sees a payable. Finance approves payment in a separate step. Pay status and bill IDs return to the store.

02

Review a refund and related work fee

A store issues a refund. The return logs in BigCommerce.

A store issues a buyer refund in BigCommerce. The refund flags a linked work fee in Wingspan. Your team checks the work and contract terms. Finance reviews the open bill before approving any change. The refund does not itself deduct worker pay.

03

Wholesale order collection to worker pay

A buyer pays a wholesale order. The funds log in BigCommerce B2B Edition.

A wholesale buyer pays an order in BigCommerce. Payment IDs match the receipt to a client invoice in Wingspan. Finance reviews related contractor payables under their own terms. Each payable needs payment approval before a pay run sends money. Client receipts and worker pay stay separate.

Plan your integration

Keep buyers and workers separate

Selected sellers, affiliates, and service workers link to worker records in Wingspan. Store shoppers stay buyer records. The worker record keeps its selected type. Contractors use payables. W-2 workers use pay statements and employee payroll with tax withholding.

Review refund effects on work fees

Your fee terms set how refunds affect service earnings. Review the related work and open bills before changing the amount owed. Finance approves the change before payment. A buyer refund does not itself debit a worker's bank account.

Choose shared order and payment fields

Use shared order IDs, bill IDs, and payment status tags to match store work to worker pay. Choose the fields your store team needs to review each linked record.

How the worker lifecycle fits

Connect worker records from hire to pay. Choose the Contractor or W-2 type and keep the right checks for each.

Workers and worker types
Selected partners link to worker records in Wingspan. Each record keeps the chosen type. Store shoppers stay buyer records.
Engagements and assignments
Work templates and worker jobs set agreed rates and checks. Store work adds project context.
Requirements and eligibility
Wingspan work templates set required checks for each worker job. Your team reviews the checks to determine assignment readiness.
Work logs and approved work
Selected service work syncs to work items. Managers review the linked work log.
Payables
Approved work or known fees create contractor bills. Finance reviews and approves payment.
Client invoices
Wholesale billing links to client invoices in Wingspan. Client billing stays separate from worker pay.
Payments and payouts
BigCommerce tracks buyer receipts. Wingspan tracks worker pay. Deposit confirmed means the sending bank or provider processed the transfer. The receiving bank handles posting the funds.
Tax forms and reporting
Wingspan holds worker tax records. Contractor 1099 totals and W-2 wages stay separate from store sales.

Connect BigCommerce to your worker workflows

Bring worker records, work review, and payments together. We’ll help you set up the flow your team needs.

Discuss your integration