How long does the FedEx integration take to ship?
Our standard window is thirty days from signed scope to live FedEx adapter in production, plus a one-week monitored stabilization phase. For Reading, Pennsylvania, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Is this a packaged FedEx 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 FedEx adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your FedEx tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
What happens if FedEx changes their API after we go live?
Our SRE team monitors FedEx 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.
Do we own the integration code at the end?
Yes. The Connectify FedEx 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 Reading, Pennsylvania. After go-live, the FedEx 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.