Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the ShipStation surface.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The ShipStation adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Do we own the integration code at the end?
Yes. The Connectify ShipStation adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Oakland, California. After go-live, the ShipStation adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
How long does the ShipStation integration take to ship?
Our standard window is thirty days from signed scope to live ShipStation adapter in production, plus a one-week monitored stabilization phase. For Oakland, California, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Is this a packaged ShipStation connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.