ConFlowIO

Shipping

Sendcloud

Sendcloud reaches many carriers through one account. One mapping turns an order into a shipment in the Shipping Bundle; which carrier creates the label is decided by the last building block.

A shipment that has already been created is not bought a second time. For parcels leaving the EU, the customs documents Sendcloud creates (commercial invoice, CN23) come back together with the label.

Demo on your own data

If Sendcloud accepts only some of the packages of a shipment, the shipment is cancelled again rather than half sent.

  1. SendcloudShipping
  2. ConFlowIOintegration platformRun active
  3. Shopware 6
  4. Kaufland
  5. JTL-Wawi
  • 8ready-made building blocks
  • 7data models in the Shipping Bundle

Building blocks

Eight building blocks for Sendcloud

  • Create shipmentsWrite

    Creates shipments with labels, several packages with one parcel and label each. A shipment already created is not bought a second time; for parcels leaving the EU, the commercial invoice and CN23 come back with it.

  • Shipping optionsRead

    Reads the shipping options your Sendcloud account offers.

  • Find service pointsRead

    Finds parcel shops and pick-up points 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.

  • TrackingRead

    Reads the state of a shipment at Sendcloud, with the delivery forecast and the time of delivery where Sendcloud provides them.

  • CancelWrite

    Cancels a created shipment.

  • Book pickupWrite

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

  • Create returnsWrite

    Creates a return with a standalone return label, without an outbound 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 Sendcloud

  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 Sendcloud
    4. Storethe labels as files

    If Sendcloud accepts only some of the parcels, the shipment is cancelled again rather than half sent.

  2. Delivery to a service point

    Your customers choose a parcel shop or pick-up point at checkout instead of their home address.

    1. Findparcel shops and pick-up points near the delivery address, as uniform records
    2. Offerthe service points at checkout
    3. Createshipment to the chosen service point, with label at Sendcloud

    If the details do not match, the shipment is rejected rather than sent to the home address.

Good to know

What to know about Sendcloud

  • PrerequisiteOne account, many carriers.
    • An account with Sendcloud
    • The credentials are stored encrypted in ConFlowIO
  • 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 Sendcloud 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