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.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Fresno, 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.
What happens if ShipStation changes their API after we go live?
Our SRE team monitors ShipStation change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
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.
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.
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.