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 Lancaster, Pennsylvania, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The FedEx adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Does it work with our existing FedEx licenses?
Yes — the adapter rides on top of your existing FedEx 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 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.
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 does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Lancaster, 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.