B2B portal: send product dimensions and SKUs in Starshipit live rate requests

aran

When the Cin7 Core B2B portal requests live rates from Starshipit, it sends only the total order weight. Length, width and height are null and there are no SKUs, even when products have dimensions set in Cin7. Support has confirmed this is how it currently works.

This means carriers can't quote on size or cubic weight, which is a real problem for bulky items. Long or oversized products can be offered parcel services they exceed the size limits for, such as Australia Post eParcel, and freight rates can come in well under the true cost.

Request: include each line item's SKU, quantity and product dimensions (from the Dimensions tab) in the Starshipit rate request. That way Starshipit can apply its Product Catalogue and packaging rules, and carriers can quote by size. A setting to turn this on per integration would be ideal.

This would help anyone selling bulky or mixed-size products through the B2B portal.

1

Comments

3 comments

  • Comment author
    mail

    Agreed we have the same issue.
    The workaround we use is storing the weights in Cin7 as the greater of cubic/actual weight. This does the trick as far as accurate quoting is concerned but still not ideal

    0
  • Comment author
    aran

    Thanks for the suggestion, that's one option we're looking at. It's not ideal as orders with heavy/dense items and large/light items together is over quoted though.

    Also other systems like Shopify do take into account the dimensions of items so we don't want to synchronise incorrect weights to other systems.

    0
  • Comment author
    Chris
    • Edited

    This is a StarShipIT problem, for years I've told them to import other details from Cin7 that falls on constantly falls on deaf ears

    • HS / HTS Codes
    • Dims
    • COO
    • Auto-convert currencies to a selected base currency using Cin7 SO header / data

    Try take a look at SSI catalogue to see if it can help fix your problem.

    I advised Cin7 that they should just make their own shipping label problem for Windows, or they should take over the integration of the Cin7 SSI (though we dont use it for other reasons and just use SSI API and manage the missing data via the SSI catalogue instead)

    0

Please sign in to leave a comment.