Question 1

What data does CommerceShip send to Supabase?

Accepted Answer

Shipment records with package dimensions, weights, and service levels. Tracking events with timestamps and delivery outcomes. Carrier charges broken out by base rate, surcharge, and accessorial. Invoice line items and audit results. Order and fulfillment records tying shipments back to the channel they came from.

Question 2

How often does data update in Supabase?

Accepted Answer

Scheduled exports run daily or weekly on the cadence you set. For anything closer to real time, delivery exceptions can post to your alerting tool as they happen on the full platform, and the REST API supports pulling records on your own schedule.

Question 3

Can I map shipping fields to my existing Supabase schema?

Accepted Answer

Yes. Map any shipment field to your own column names and apply transforms during export, so data arrives in the shape your existing models expect. You do not need to restructure Supabase tables or rewrite downstream queries to take shipping data.

Question 4

Do I still get reporting inside CommerceShip?

Accepted Answer

Yes. Pre-built dashboards cover orders, shipments, carrier service, transit times, charges, and savings, with filtering by customer, carrier, service, and period. Exporting to Supabase is for joining shipping data to the rest of your business data, such as revenue, margin, and customer lifetime value.

Question 5

Does this write to my Supabase tables or its own?

Accepted Answer

Its own by default, named so they are obvious, which keeps shipping data out of the tables your application depends on. Point the sync at existing tables instead if you would rather it write into a schema you already maintain.

Question 6

How are updates handled in Supabase?

Accepted Answer

By upsert on the record key, so a shipment that changes status updates its existing row, and nothing is appended twice. Only records that changed since the last run are written.

Question 7

What access does CommerceShip need to Supabase?

Accepted Answer

The connection uses scoped credentials limited to the record types the integration works with, and you choose which fields are included. Credentials are encrypted at rest and stored separately from your operational data. Revoke the connection from either side at any time and the access ends with it.

Question 8

How is my data protected?

Accepted Answer

TLS in transit and AES-256 at rest, with tenant isolation enforced by row-level security in the database. Role-based permissions control who on your team can see cost data or change carrier settings, and automated actions are written to an audit log. CommerceShip is pursuing SOC 2 Type II certification. The security page carries the full detail.

Type	Format	Rows	Status
Invoice Audit	csv	1,284	Pending
Finance Invoices	csv	312	Pending
Invoice Audit	csv	5,902	Pending

Sync supply chain data into Supabase

Supabase Integration Capabilities

How the Supabase integration works

Connect Supabase

Choose fields and cadence

Keep Supabase current

Supabase Integration FAQs

Export supply chain data to Supabase

Other Data Destinations