ConFlowIO

Shipping

FedEx

ConFlowIO books through your own FedEx account and gives prices and transit times in advance. Outside the EU, FedEx creates the commercial invoice along with it; labels come as PDF or for label printers (ZPL).

Locations, pickups and return labels have building blocks of their own. Before the first real shipment, FedEx requires the labels to be checked.

Demo on your own data

A pickup already booked for that day and address is recognised.

  1. FedExShipping
  2. ConFlowIOintegration platformRun active
  3. Xentral
  4. Salesforce Commerce Cloud
  5. Amazon
  • 9ready-made building blocks
  • 7data models in the Shipping Bundle

Building blocks

Nine building blocks for FedEx

  • Create shipmentsWrite

    Books shipments through your own FedEx account, several packages with one parcel and label each; outside the EU with a commercial invoice. Labels as PDF or for label printers (ZPL).

  • Return labelWrite

    Creates a standalone return label with FedEx, without an outbound shipment.

  • Look up ratesRead

    Gives prices and transit times for a shipment in advance.

  • Find locationsRead

    Finds FedEx locations near an address as uniform records — to offer them at checkout, for instance. A shipment can be addressed there; if the details do not match, it is rejected rather than sent to the home address.

  • Book pickupWrite

    Books a pickup with FedEx; one already booked for that day and address is recognised.

  • Cancel pickupWrite

    Cancels a booked pickup.

  • TrackingRead

    Reads the state of a shipment at FedEx, with the delivery forecast and the time of delivery where FedEx provides them, and, where available, who accepted the parcel. On explicit request, it stores the proof of delivery with signature as a file.

  • CancelWrite

    Cancels a booked shipment.

  • Free request

    For anything without a ready-made building block: a request to the API, using the stored credentials.

In practice

Two workflows with FedEx

  1. Shipping label for an order

    One mapping for every carrier, instead of one per carrier.

    1. Readorders from shop, marketplace or ERP
    2. Maporder onto a shipment with its packages in the Shipping Bundle
    3. Createone parcel with label per package at FedEx
    4. Storethe labels as files

    One mapping for every carrier, including shipments outside the EU.

  2. Costs before booking

    Which service a shipment is booked with should depend on the price.

    1. Maporder onto a shipment in the Shipping Bundle
    2. Look upprices and transit times at FedEx
    3. Choosethe service by your rule
    4. Createshipment with label at FedEx

    The service is chosen before booking, not noticed on the invoice afterwards.

Good to know

What to know about FedEx

  • PrerequisiteA contract on your side.
    • A business customer contract with FedEx
    • FedEx's approval for API access
    • A label check by FedEx before the first real shipment
  • Shipping BundleA Shipping Bundle of its own describes shipments, packages, parcels, service points, shipping rates and pickups uniformly, the same for every carrier.
    • One mapping turns an order into a shipment
    • Which carrier creates the label is decided by the last building block
    • Several packages are created with one parcel and label per package
    • Changing carrier leaves the mapping untouched
  • DurabilityApplies to this integration as to every workflow in ConFlowIO.
    • Failed steps retry themselves
    • Large reads are processed page by page, each page a step of its own
    • A failed run is continued rather than started over
    • Live logs per step, with credentials removed

Contact

See FedEx on your own data

We are glad to show ConFlowIO on your own data. Bring a real slice of your orders.

The difference shows at real volumes — not at five sample records.

Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.

Rather write directly?info@conflowio.com