Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
ERP · Two-way sync platform

Rootstock ERP integration.

Connect your Rootstock ERP workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Bills of Material, Items / Products and Sales Orders.

Set this up from Claude or ChatGPT
  • Review your systems with an integration engineer
  • Get a scoped implementation and validation plan

Adopted by fast-scaling companies moving mission-critical data in real time

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
Record types

Rootstock ERP records to discuss.

These Rootstock ERP record examples help scope a technical review. They are not a list of verified Stacksync operations.

Sales Orders
Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Work Orders
Identify this record type and the operation you need to review with Stacksync.
Purchase Orders
Retain purchase-order and line IDs together with the supplier and legal-entity context.
See 3 more record examples
Items / Products
Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Bills of Material
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Inventory Balances
Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
Connection setup

Rootstock ERP connection requirements.

Review Rootstock ERP access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion.

Prepare access and scope for the engineering review
  • 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.

Integration design

Match records and fields for your Rootstock ERP integration.

Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references.

Use these design questions to prepare a representative record and the business rules your integration must preserve.

Explore record matching and field-mapping checks
Rootstock ERPSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Load related records in the right order
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.

Mapping checks by record type

Bills of Material

Confirm object support with Stacksync

Identity
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Fields to consider
Source bill ID · Supplier reference · Entity · Line amounts and currency · Approval/posting state
Related records to resolve first
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Test before going live
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Items / Products

Confirm object support with Stacksync

Identity
Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Fields to consider
Source product ID · SKU or variant reference · Description · Unit of measure · Price-list reference
Related records to resolve first
Resolve units, variants, categories, and applicable price lists before order lines.
Test before going live
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

Sales Orders

Confirm object support with Stacksync

Identity
Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Fields to consider
Source order ID · Customer reference · Line references and quantities · Order status · Currency
Related records to resolve first
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test before going live
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

Purchase Orders

Confirm object support with Stacksync

Identity
Retain purchase-order and line IDs together with the supplier and legal-entity context.
Fields to consider
Source purchase-order ID · Supplier reference · Line references · Quantity · Approval status
Related records to resolve first
Resolve supplier, product, business unit, and delivery-location references before lines.
Test before going live
Test a partially received purchase order and an amendment after approval.

Inventory Balances

Confirm object support with Stacksync

Identity
Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
Fields to consider
Product reference · Location reference · Quantity type · Quantity · As-of time
Related records to resolve first
Resolve product, unit, warehouse/location, and lot/serial references.
Test before going live
Test the same SKU in two locations, a reservation, and an older snapshot arriving late.

Receipts and Shipments

Confirm object support with Stacksync

Identity
Retain shipment/fulfillment and line IDs, order reference, and carrier context.
Fields to consider
Source shipment ID · Order/line references · Carrier · Tracking reference · Fulfillment status
Related records to resolve first
Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
Test before going live
Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Rootstock ERP integration in four steps.

Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

View the four setup tests and expected results

  1. Confirm the intended Rootstock ERP account and grant

    After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity.

    Expected result: The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure.

  2. Test record matching for Bills of Material

    Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

    Expected result: Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

  3. Test the operation your workflow needs

    Review one Rootstock ERP record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Rootstock ERP integration.

Diagnose record matching, delayed changes, and rejected operations
A Rootstock ERP record appears under the wrong destination record
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines. Repair the ID relationship before repeating the operation.
The first load looks correct but later results differ
Confirm the selected Rootstock ERP implementation’s change-detection method for Bills of Material, Items / Products and Sales Orders. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture.
One operation succeeds while another is rejected
Check the specific Rootstock ERP object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Rootstock ERP workflow with an engineer

Rootstock ERP integration guides

FAQ

Rootstock ERP connector FAQ

How should I plan an integration with Rootstock ERP?

Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Rootstock ERP connector write changes back?

Write-back support is not established for this connection. Review the Rootstock ERP records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

Which identifiers should I preserve for Rootstock ERP data?

Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.

Which related records should I load first for Rootstock ERP?

Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.

How do I validate Rootstock ERP changes after the initial load?

Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

What will we cover in a Rootstock ERP integration demo?

Start with one workflow and a sample record from Bills of Material, Items / Products and Sales Orders. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

AI assistant

Set up Rootstock ERP from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my Rootstock ERP and another app or database.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Rootstock ERP. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a Rootstock ERP record changes.”
  • “Create a Genie that answers questions about our Rootstock ERP data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

Explore Rootstock ERP connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

156 integration guides

CRM · 30

ERP · 24

Database · 12

Data warehouse · 9

Business productivity · 22

Accounting and finance · 13

AI · 4

Analytics · 6

E-commerce · 6

Human resources · 12

Marketing · 8

Security and identity · 6

Storage · 4

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

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:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started