It starts with
one item.

Understand your ERP. Trace what went wrong, manage the change, and verify the result with CrossCheck.

Find the cause. See what it affects.

An availability rule points to the wrong location. CrossCheck connects the rule, its dependencies and the records it affects, so you can trace the issue in context.

Fix the setting behind the symptom.

The wrong location lives in one availability setting. Before anything ships, CrossCheck shows the one-line change, the objects it reaches and the tests linked to it.

Ship it the governed way.

Approval, a dry run and a backup come before the deploy, and verification follows it. Each step is recorded, and a rollback stays ready until the change is confirmed.

Test the process the change touches.

After the deploy, one test run follows an order through stock, the sales order and fulfillment, so the fix is checked in the records it reaches.

Confirm the outcome. Keep the record.

What changed. Why it changed. What happened next. An operating history gives the next investigation context, rather than leaving the team to reconstruct it from scratch.

Script PerformanceInventory availabilityProduction · 7 days
P95
1.9s
Usual
420ms
Runs
84
Example Script Performance module: after a deployment, runs of the inventory availability script slowed. P95 is 1.9 s against a usual 420 ms.
ChangeAvailability settingIn review
− location: warehouse_b+ location: warehouse_a
Changes
1
Affected objects
3
Linked tests
3
Example change: the availability setting moves from warehouse_b to warehouse_a, reaching three objects and three linked tests.
Release runRP-142 · v4Production
Elapsed
2:36
Changed objects
1
Rollback
Ready
Example release run: CrossCheck summarizes the change, then it is approved, backed up, deployed and verified in Production.
Test runOrder → Fulfillment3 cases
  1. Check stockIR-1042
  2. Create orderSO-1042
  3. FulfillIF-1042
Passed
3 / 3
Duration
3.1s
Failed
0
Example test pipeline: after the deployment, three cases check stock, create a sales order and fulfill it.
OutcomeInventory availabilityVerified
P95
1.1×
Tests
3 / 3
Record
RP-142
Example outcome: after RP-142, P95 returned to its usual range and all three tests passed. The release record keeps both.

Our models, at work inside CrossCheck.

Our models grow in three steps. Inside CrossCheck they already read each script, measure how it runs and coordinate the work across your business.

  1. Understands it

    Reads what each script does and what it means for the business.

  2. Detects it

    Measures how each script runs and catches the one that drifts.

  3. Orchestrates it

    Coordinates the workflows that run across the business.

From operating context to process intelligence.

CrossCheck connects us to real ERP operations. Their data and context form the foundation for MONIAC, a model we are developing to understand how business processes work.

Explore MONIAC
Illustration: three layers of work inside CrossCheck, understanding, detecting and orchestrating, stack up beneath MONIAC, a model in development.

Works with the platforms you run.

Start with NetSuite or Shopify. CrossCheck connects to your account and works with the records you already have.

  • NetSuite

    Investigate issues and review AI-proposed changes, then test, deploy and monitor them in one place, with approvals and test gates.

    View on SuiteApp.comOpens in a new tab
  • Shopify

    Back up your store’s products, orders and settings, see what changed, and restore it when you need to.

    Try it on Shopify

Start with one system. Build toward something larger.

Start with NetSuite. Work toward intelligence across more enterprise systems.