Does it work with our existing ShipStation licenses?
Yes — the adapter rides on top of your existing ShipStation subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
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 Tempe, Arizona, 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.
Can the ShipStation adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your ShipStation tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
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 Tempe, Arizona. 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.