Can you integrate Rootstock ERP with Supabase?

Explore a Rootstock ERP and Supabase integration with a Stacksync engineer. Stacksync support for Rootstock ERP and Supabase is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can Rootstock ERP and Supabase sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the Rootstock ERP and Supabase initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Rootstock ERP account, edition, environment, and business objects the integration must access. Identify the Supabase account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Rootstock ERP to Supabase sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map Rootstock ERP fields to Supabase?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a Rootstock ERP and Supabase integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the Rootstock ERP and Supabase pilot start with?

Start by reviewing Bills of Material in Rootstock ERP and Proposed supplier bill table in Supabase (choose its name) in Supabase. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

ERP / Database · Two-way sync platform

Rootstock ERP and Supabase integration

Plan how Rootstock ERP and Supabase should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Rootstock ERP

Supabase

Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study

Migrated from MuleSoft

Case study

Migrated from Celigo

Migrated from Heroku Connect

Migrated from Matillion

Case study

Migrated from Fivetran

Case study

Migrated from Celigo

Proposed workflow

Supplier bill reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Rootstock ERP Bills of Material or the proposed supplier bill table in Supabase needs a defined result in the other system.

Start with Rootstock ERP Bills of Material and the proposed supplier bill table in Supabase. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Rootstock ERP and Supabase
Rootstock ERP record	Supabase record	Record matching	Field ownership
Bills of MaterialProposed record; confirm Stacksync object support.Reporting dataset	Proposed supplier bill tableProposed table; choose its name and schema.	Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.	Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.
Sales OrdersProposed record; confirm Stacksync object support.Reporting dataset	Proposed sales order tableProposed table; choose its name and schema.	Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.	Decide which system approves the order and which can cancel or amend it after fulfillment begins.
Items / ProductsProposed record; confirm Stacksync object support.Reporting dataset	Proposed product or catalog item tableProposed table; choose its name and schema.	Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.	Assign ownership for catalog content, price, and stock separately.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Rootstock ERP

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Sales Orders Work Orders Purchase Orders Items / Products Bills of Material Inventory Balances	Confirm support for this record type and the direction you need.

Discuss Rootstock ERP requirements

Supabase

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Tables Views Schemas auth.users Row Level Security Policies JSONB Columns	Confirm support for this record type and the direction you need.

Discuss Supabase requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	Rootstock ERP	Supabase
Integration interface	Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects	Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
Authentication	Confirm the credentials, API plan, and permissions required for Rootstock ERP.	Confirm the credentials, API plan, and permissions required for Supabase.
Change detection	Confirm how Stacksync detects changes for this connector and the objects you need.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Confirm with Stacksync	Confirm with Stacksync
Write access	Confirm with Stacksync	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Rootstock ERP

Integration interface: Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
Authentication: Confirm the credentials, API plan, and permissions required for Rootstock ERP.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Rootstock ERP account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Rootstock ERP, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Rootstock ERP and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Supabase

Integration interface: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
Authentication: Confirm the credentials, API plan, and permissions required for Supabase.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Supabase account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Supabase, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Supabase and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Rootstock ERP and Supabase access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Rootstock ERP setup checklist

Identify the Rootstock ERP account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Rootstock ERP, including read/write support, authentication, and initial-load limits.

Supabase setup checklist

Identify the Supabase account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Supabase, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Rootstock ERP and Supabase planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Reporting dataset

Bills of Material / Proposed supplier bill table in Supabase (choose its name)

Plan a supplier bill dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rootstock ERP: Object support to establish
Supabase: Your database schema
Record identity: Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Field ownership: Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

Fields to include

Source bill ID
Supplier reference
Entity
Line amounts and currency
Approval/posting state

Record dependencies: Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Validation: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Recovery: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

Reporting dataset

Sales Orders / Proposed sales order table in Supabase (choose its name)

Plan a sales order dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rootstock ERP: Object support to establish
Supabase: Your database schema
Record identity: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership: Decide which system approves the order and which can cancel or amend it after fulfillment begins.

Fields to include

Source order ID
Customer reference
Line references and quantities
Order status
Currency

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Reporting dataset

Items / Products / Proposed product or catalog item table in Supabase (choose its name)

Plan a product or catalog item dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rootstock ERP: Object support to establish
Supabase: Your database schema
Record identity: Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Field ownership: Assign ownership for catalog content, price, and stock separately.

Fields to include

Source product ID
SKU or variant reference
Description
Unit of measure
Price-list reference

Record dependencies: Resolve units, variants, categories, and applicable price lists before order lines.
Validation: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Recovery: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Reporting dataset

Inventory Balances / Proposed inventory or stock position table in Supabase (choose its name)

Plan a inventory or stock position dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rootstock ERP: Object support to establish
Supabase: Your database schema
Record identity: Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
Field ownership: Choose the stock authority and distinguish available, reserved, and physical quantities.

Fields to include

Product reference
Location reference
Quantity type
Quantity
As-of time

Record dependencies: Resolve product, unit, warehouse/location, and lot/serial references.
Validation: Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
Recovery: Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.

Reporting dataset

Receipts and Shipments / Proposed shipment or fulfillment table in Supabase (choose its name)

Plan a shipment or fulfillment dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rootstock ERP: Object support to establish
Supabase: Your database schema
Record identity: Retain shipment/fulfillment and line IDs, order reference, and carrier context.
Field ownership: The fulfillment owner controls shipped quantities and cancellation eligibility.

Fields to include

Source shipment ID
Order/line references
Carrier
Tracking reference
Fulfillment status

Record dependencies: Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
Validation: Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
Recovery: Verify existing fulfillment before retrying creation; reconcile quantities against order lines.

Reporting dataset

Purchase Orders / Proposed purchase order table in Supabase (choose its name)

Plan a purchase order dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Rootstock ERP: Object support to establish
Supabase: Your database schema
Record identity: Retain purchase-order and line IDs together with the supplier and legal-entity context.
Field ownership: Keep procurement approval separate from receipt and payment states.

Fields to include

Source purchase-order ID
Supplier reference
Line references
Quantity
Approval status

Record dependencies: Resolve supplier, product, business unit, and delivery-location references before lines.
Validation: Test a partially received purchase order and an amendment after approval.
Recovery: Reconcile receipts already recorded before resubmitting an amended order.

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Bills of Material / Proposed supplier bill table in Supabase (choose its name) to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Rootstock ERP and Supabase record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Bills of Material / Proposed supplier bill table in Supabase (choose its name), update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when Rootstock ERP and Supabase need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time Rootstock ERP / Supabase migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Supplier bill reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Bills of Material or Proposed supplier bill table in Supabase (choose its name) record needs a defined result in the other system.

Start with Rootstock ERP Bills of Material and Supabase Proposed supplier bill table in Supabase (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

Sales order reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Sales Orders or Proposed sales order table in Supabase (choose its name) record needs a defined result in the other system.

Start with Rootstock ERP Sales Orders and Supabase Proposed sales order table in Supabase (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Product or catalog item reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Items / Products or Proposed product or catalog item table in Supabase (choose its name) record needs a defined result in the other system.

Start with Rootstock ERP Items / Products and Supabase Proposed product or catalog item table in Supabase (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve units, variants, categories, and applicable price lists before order lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

If it fails: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Reconcile Rootstock ERP business records with Supabase

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Rootstock ERP needs operational visibility through a selected destination dataset.

Select Sales Orders or Purchase Orders with the correct legal entity, period, and currency.
Define a reporting relationship in Supabase; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Bills of Material / Proposed supplier bill table in Supabase (choose its name)

Test case

Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Expected result

The expected supplier bill relationship is preserved with no duplicate action or unintended write.

Sales Orders / Proposed sales order table in Supabase (choose its name)

Test case

Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

Expected result

The expected sales order relationship is preserved with no duplicate action or unintended write.

Items / Products / Proposed product or catalog item table in Supabase (choose its name)

Test case

Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

Expected result

The expected product or catalog item relationship is preserved with no duplicate action or unintended write.

Inventory Balances / Proposed inventory or stock position table in Supabase (choose its name)

Test case

Test the same SKU in two locations, a reservation, and an older snapshot arriving late.

Expected result

The expected inventory or stock position relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated supplier bill change

Investigate

Inspect Rootstock ERP Bills of Material and Supabase Proposed supplier bill table in Supabase (choose its name), their IDs, and the destination error.

Next action

Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

Rejected or repeated sales order change

Investigate

Inspect Rootstock ERP Sales Orders and Supabase Proposed sales order table in Supabase (choose its name), their IDs, and the destination error.

Next action

Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Rejected or repeated product or catalog item change

Investigate

Inspect Rootstock ERP Items / Products and Supabase Proposed product or catalog item table in Supabase (choose its name), their IDs, and the destination error.

Next action

Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

A record type or update is unavailable

Investigate

Check the Rootstock ERP and Supabase connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Rootstock ERP and Supabase

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Rootstock ERP Supabase Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Supabase.

Supabase Rootstock ERP Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Rootstock ERP.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ