Sendcloud / nShift Shipping Platform Connector

主な機能

Connects Business Central to Sendcloud, nShift (Ship / Transsmart) or EasyPost via their REST APIs — pick one platform or several

Reaches 100+ carriers through a single platform integration instead of one-off per-carrier AL development

AL table and page extensions on Sales Order, Warehouse Shipment and Posted Sales Shipment with a 'Create Shipment / Get Label' action

Label PDF retrieval written back to the BC document, ready to print to your label printer

Customs document generation (CN22 / CN23, commercial invoice data) for cross-border and non-EU shipments

Service-point selection and per-carrier delivery-method picker surfaced directly on the order

Return-label generation in one click from posted shipments

Tracking-number sync and live delivery-status polling via a scheduled Job Queue entry

Dedicated setup page for platform API credentials, default carrier mapping, and weight/dimension source fields

Carrier and delivery-method mapping rules so the right service is auto-selected from order data (country, weight, value)

Per-tenant extension with its own permission set — no source handed to third parties, fully under your tenant governance

Optional Power Platform / Dataverse surfacing of tracking status for portals or Power BI shipping dashboards

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Dynamics 365 Business Central 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

Instead of wiring Business Central to every carrier one painful API at a time, this connector bridges BC to a shipping platform — Sendcloud, nShift (Ship / Transsmart) or EasyPost — so a single integration unlocks 100+ carriers and their delivery methods.

ECOSIRE builds this as a per-tenant AL extension installed directly on your Business Central environment (cloud or on-prem). It adds table and page extensions to Sales Order, Warehouse Shipment and Posted Sales Shipment, plus a setup page holding your platform API credentials, default service points and carrier-mapping rules. Event subscribers fire on shipment posting (or on demand) to call the platform's REST API, create the parcel, and write the returned tracking number, label PDF and customs documents (CN22/CN23 for cross-border) back onto BC records.

Operators get a "Create Shipment / Get Label" action on the document, a service-point and delivery-method picker for the chosen carrier, and one-click return-label generation. Inbound tracking status syncs back via a scheduled Job Queue entry that polls the platform, so order and warehouse staff see live delivery state without leaving BC.

Because it is your code on your tenant, we tailor field mappings, weight/dimension sources, multi-package logic and which platform(s) you connect. We scope against your real carrier contracts and BC localization, build it, install it with a dedicated permission set, and support it after go-live. This is honest custom work — not an instant Microsoft AppSource download. You get a defined lead time, a working extension on your environment, and a named team to maintain it as platform APIs and your carrier mix evolve.

得られるもの

Per-tenant AL extension (.app) built for your Business Central version and installed on sandbox then production

Shipping Platform Setup page with credential storage, carrier mapping and default-service configuration

Dedicated BC permission set scoped to the shipping actions and setup

Configured Job Queue entry for automated tracking-status polling

Field-mapping and carrier-rule configuration matched to your contracts and BC localization

Handover documentation: operator guide, setup reference, and platform-credential runbook

これは誰のためのものですか

Logistics / Warehouse Manager

Ships across many carriers and wants one consistent label-and-tracking flow inside BC rather than juggling separate carrier portals.

Operations Director at a mid-market shipper

Wants platform-level carrier breadth (100+ carriers via Sendcloud/nShift/EasyPost) without committing to a year of in-house AL integration work.

Business Central Administrator / IT Lead

Needs a governed per-tenant extension with a clean permission set, predictable updates, and a vendor who supports it — not orphaned custom code.

Sendcloud / nShift Shipping Platform Connector の比較方法

基準	エコシエール	カスタムビルド	競合他社	Dynamics 365 Business Central 標準機能
Reach 100+ carriers through one integration	付属	部分的なサポート	部分的なサポート	含まれていない
Built and tailored to your carriers, fields and BC localization	付属	付属	含まれていない	含まれていない
Installed as a governed per-tenant extension with its own permission set	付属	部分的なサポート	付属	含まれていない
Label, customs-doc and return-label retrieval written back to BC	付属	部分的なサポート	部分的なサポート	含まれていない
Tracking-status sync via scheduled Job Queue	付属	部分的なサポート	部分的なサポート	含まれていない
Vendor-supported through platform-API and BC version changes	付属	含まれていない	部分的なサポート	部分的なサポート
No long in-house AL development project required	付属	含まれていない	付属	付属
Multi-platform routing (Sendcloud + nShift + EasyPost) configurable	付属	部分的なサポート	含まれていない	含まれていない

Sendcloud / nShift Shipping Platform Connector に関するよくある質問

How long does delivery take and what does the build-to-order process look like?

After purchase we run a short scoping call to confirm your platform (Sendcloud, nShift or EasyPost), carrier contracts, BC version and localization. Typical delivery is about 2 to 4 weeks depending on how many platforms and carrier-mapping rules you need. We build in a sandbox, demo it to you, then install on production. You get a firm timeline at scoping — this is custom work delivered to your tenant, not an instant AppSource download.

Is this on Microsoft AppSource? Can I just download it?

No. This is a build-to-order per-tenant extension. ECOSIRE builds the AL extension specifically for your environment, configured to your carriers and field mappings, and installs it on your Business Central tenant (or on-prem). There is no public AppSource listing or self-serve download — that is deliberate, because the value is in tailoring it to your shipping setup.

What happens with ongoing support and updates after go-live?

We support the extension after installation. If a platform changes its REST API, BC releases a new major version, or you add carriers and delivery methods, we maintain the connector under a support arrangement agreed at handover. Because it is your code on your tenant, you are never locked out — you hold the extension, the setup, and the documentation.

Can I connect more than one shipping platform at the same time?

Yes. The connector is designed so you can route to Sendcloud, nShift or EasyPost — and we can wire multiple platforms with mapping rules that pick the right one per shipment (for example, EasyPost for US domestic, Sendcloud for EU). That multi-platform routing is part of the scoping conversation since it depends on your contracts.

Will it work with my existing carrier accounts and contracts?

Yes. You keep your own carrier accounts and negotiated rates inside the shipping platform; the connector authenticates to your platform account via API credentials on the setup page. We map your order data (weight, dimensions, value, destination) to the correct carrier service so your existing contracts are honored.

Does it write tracking and customs documents back into Business Central?

Yes. On shipment creation the platform returns a tracking number, label PDF and — for cross-border — customs documents (CN22/CN23), all written back onto the BC shipment record. A scheduled Job Queue entry then polls the platform so live delivery status is visible inside BC without opening the carrier portal.