Shipsy×EMBRAER

Confidential

Aftermarket Logistics

This microsite is confidential and prepared for Embraer. Please enter the password to continue.

Shipsy×EMBRAERGlobal Logistics Integrated Solution

Aftermarket Logistics

Standardise and automate Embraer's aftermarket logistics

One connected way to plan, ship, track and reconcile across all five DCs — on top of SAP, orchestrating your existing carriers.

See our understanding Jump to the solution
Confidential · Prepared for Embraer AftermarketShipsy

Agenda for today

What we'll cover

01
Introduction
Team & context
5min
02
Shipsy Overview & Credentials
Who we are · scale · analyst recognition · proof
5min
03
Our Understanding of Embraer's Problem Statement
What we heard in the RFI · the as-is outbound process
5min
04
Shipsy Solution Overview
One control tower across every aftermarket flow
60min
05
Q&A / Next Steps Alignment
Open questions & the path forward
15min
Shipsy team joining the session today
Shipsy — The Enterprise Standard for AI-Native Logistics
Shipsy global customer footprint
Gartner recognition — highest-rated TMS vendor
Case study — argenx global pharma logistics
Case study — Catalent reliability at scale
Case study — Leading electronics retailer

Our Understanding

Embraer is looking for a partner to standardise and automate its aftermarket parts logistics — one digital control tower across five distribution centres.

Our understanding of the situation
  • Global aftermarket (spare-parts) logistics to 100+ countries from five DCs — Brazil, USA, France, Singapore, China — each on a different system, so no standard process or single view.
  • Core problem is manual, fragmented execution — labels/AWBs by hand, data re-keyed between SAP and each carrier app, freight invoices validated manually.
  • Limited carrier integration & no end-to-end tracking — no consolidated visibility, no carrier-performance view, low inbound ASN adoption.
  • Flows to cover: outbound, inbound, intercompany, repair & reverse, plus import/export compliance (Customs, ITN/AES, HTS, COO).
  • Must sit on top of SAP (ECC → S/4HANA 2028) and integrate with carrier EDI, Salesforce, OGTM & SSO — orchestrating incumbent carriers, not replacing them.
As-is · Outbound & Intercompany (today)

How Embraer ships a part today — to a customer or between its own sites

The systems involved today — none of them connected
SAP ECC

Order · pick/pack · invoice

System of record

Outlook

Email coordination

Planning, approvals, chasing

Carrier apps

One portal per carrier

FedEx · DHL · DSV · K+N …

Excel

Freight audit

Manual, weeks later

Every outbound — to a customer, between sites, or a planned transfer — runs the same manual gauntlet: SAP + Outlook + a separate app per carrier + Excel. The AWB is keyed twice and there is no single view of any shipment.

Outside Shipsy — the order comes from here

Q&A & open discussion

The floor is yours — let's talk it through.