Tessera RP
PX-09
Sources
Where the data comes from.
Seven connectors ship today. The rest are names on a roadmap, and they are marked as such — a compatibility list that does not distinguish the two is a list you cannot plan against.
Shipping today
Source | How it reads | Notes |
|---|---|---|
Dynamics 365 Finance & Operations | SQL — BYOD, Data Lake staging, or an AxDB read replica | Every stream scoped by legal entity. Refuses to run without one rather than defaulting to all |
Dynamics 365 Business Central | OData v2 | Companies, dimensions and the full sales/purchase ledger |
NetSuite | SuiteQL | Token-based auth; saved-search parity without the saved search |
Acumatica | Contract-based REST | Generic inquiry endpoints for the heavy streams |
Shopify | GraphQL Admin API | Orders, fulfilments, refunds, and the shop's own timezone |
Amazon Selling Partner | SP-API | Orders and the settlement report, which is where the real fees are |
CSV / flat file | Upload | The budget, the dealer list, the supplier scorecard — everything the ERP does not hold |
Generic REST | Configured endpoint | For the internal service nobody wrote a connector for |
On the roadmap
Source | Status |
|---|---|
SAP Business One | Schema-ready — already a value in the source enum |
Odoo | Schema-ready — already a value in the source enum |
SAP S/4HANA | Planned |
Oracle Fusion Cloud ERP | Planned |
Sage Intacct | Planned |
Infor CloudSuite | Planned |
Epicor Kinetic | Planned |
QuickBooks Online | Planned |
eBay · Walmart Marketplace | Planned |
BigCommerce · WooCommerce · Adobe Commerce | Planned |
SFTP drop · Google Sheets | Planned |
Named because the layering makes them cheap, not to imply a partnership. A new source is one interface and one mapper — the canonical schema, the 229 metrics and every dashboard above are untouched.
What every connector does, whoever wrote it
Incremental by watermark
A per-stream cursor persisted after every page, so an interrupted run resumes instead of restarting.
Writes nothing unchanged
A content hash skips records that have not moved. 307 records pulled, 0 written, is a healthy run.
Survives drift
Raw payloads land as JSONB, so a new field upstream never fails a sync.
Quarantines rather than crashes
An unmappable record goes to a dead-letter queue, inspectable and replayable, and the sync carries on.
Respects the source
Backoff with jitter, and Retry-After honoured — a connector that hammers a production ERP gets switched off by its owner.
Tells you when it is unwell
Consecutive-failure tracking flips a connection to degraded, and freshness is shown on the tiles that depend on it.
Runs without credentials
Every connector has a mock mode, so the product can be evaluated end to end before anyone opens a firewall.