Shipsy

Confidential

Aftermarket Logistics

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

Who’s joining
Session
Shipsy

Standardise and automate Embraer's aftermarket logistics

Discussion document · Global Logistics Integrated Solution
July 2026
Prepared forEMBRAER
Embraer aircraft at the hangar
Shipsy

Agenda for todayAgenda for today

What we'll coverPicking up where we left off

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 · their network and where it reaches its limit
5min
04
Shipsy Solution Overview
One control tower across every aftermarket flow
60min
05
Integration
How Shipsy sits in the landscape and connects to SAP, OGTM and the operator network
5min
06
Q&A / Next Steps Alignment
Open questions & the path forward
10min
01
Recap of the Last Session
What we covered last time · what's still open
2min
02
Shipsy Solution Overview
Live product demonstration across the aftermarket flows
30min
03
Integration
How Shipsy connects to SAP, OGTM and the logistics operators
10min
04
Q&A / Next Steps
Open questions & the path forward
15min
Shipsy
01

Introduction

The Shipsy team joining you today, and the context for this conversation.

01
ShipsyShipsy team joining the session todayShipsy team joining the session today
Shipsy
02

Overview & Credentials

Who Shipsy is — scale, analyst recognition, and proof in air and cross-border logistics.

02
Shipsy — The Enterprise Standard for AI-Native Logistics
ShipsyShipsy global customer footprint
ShipsyGartner recognition — highest-rated TMS vendor
ShipsyThe Shipsy DNA — driving strategic partnerships in an AI-first world
Case study — LATAM Airlines: E2E cross-border eCommerce logistics on Shipsy
Case study — Teleport (AirAsia): Southeast Asia's largest air-logistics network on Shipsy
Shipsy
03

Understanding the Problem

The network we are solving for, and the problems the RFI describes.

03
Shipsy

Our understanding · the network

Embraer’s aftermarket network

Five distribution centres serving operators and MROs in over 100 countries — each DC on its own logistics system today, with air-based movements between them.

5
Distribution centres
Brazil · USA · France · Singapore · China
5
Different logistics systems
one per DC, each with different functionality
100+
Countries served
with time-critical spare parts
4
Flows in scope
outbound · inbound · intercompany · repair
NORTH AMERICA~60% of demandEUROPE~25% of demandLATIN AMERICAhome marketMIDDLE EAST & AFRICAgrowingASIA-PACIFICgrowing ✈✈✈✈✈ ★Fort Lauderdale / Fort WorthUSA - Americas DC · largest stocking nodeSao Jose dos CamposBRAZIL - Global HQ · master warehouseParis (Villepinte / Le Bourget)FRANCE - Europe DCBeijingCHINA - China DCSingaporeSINGAPORE - Asia-Pacific hub
Carriers to
orchestrate
FedExDHLDSV / DB SchenkerKuehne+Nagel Sterling CourierHoyaPhoenix Logística + customs brokers & forwarders per lane
Air-first and time-critical — an AOG part moves on the fastest route available, not the cheapest.
Shipsy

Our understanding · the problems

Where the current process reaches its limit

Network

No standard process across the five DCs

  • A different logistics system per DC, each with different functionality
  • No common shipment data, so no view of the network as a whole
  • Orders triggered across SAP and Outlook, differently at each site
  • Warehouse operations run from a SAP console, with no logistics layer above it
Shipment creation

Labels and AWBs made by hand

  • Manual shipping-label creation — the first pain named in the RFI
  • The shipment is re-typed into each carrier’s own portal to raise the AWB
  • The AWB is then keyed back into SAP a second time
  • Bill-to and ship-to are checked by hand before the parcel is handed over
Carriers

Limited carrier integration

  • Low automation across the seven named carriers
  • No real-time status flowing back from the carrier
  • No carrier-performance view — on-time delivery, transit time, exceptions
  • Contracted rates and transit times live in contracts, not in a system
Visibility

No end-to-end tracking

  • Status checked carrier by carrier, portal by portal
  • Customers and requestors updated only when someone chases
  • Inbound is weaker still — low ASN adoption, little visibility before arrival
  • Proof of delivery is captured manually, in no standard form
Finance

Freight invoices validated by hand

  • Monthly charges arrive as a report and are checked line by line in Excel
  • Rates compared against contract manually; disputes handled over e-mail
  • FRS posting and a control spreadsheet close the loop
  • True freight cost is only known weeks after the parts moved
Compliance & documents

Carried manually on every leg

  • Customs, ITN/AES, HTS and country of origin on every international move
  • Documents printed, signed, photocopied and filed in an archive bin
  • No link from the AWB and tracking number back to the PO, invoice and part
  • Export checks sit outside the shipping flow — in OGTM, or as a manual step
Source: the current-pain points named in the RFI, and the five as-is flows in Annex A — repair, intercompany, vendor, payment and the detailed outbound process.
Shipsy
04

The Shipsy Solution

One platform across every aftermarket flow — outbound, inbound, returns & repair.

04
Shipsy

Outside Shipsy — the order comes from here
Shipsy

Process State | Aftermarket Order & Planning Manager

Takes every movement from order intake, through planning, to the carrier booking

Three data entries become zero
Current State
Orders and transfers raised in SAP, chased over Outlook
Backorder, transfer and repair PO tied to no shipment
Carrier and service chosen by whoever is shipping
A different courier app for every carrier
AWB typed back into SAP by hand
Future State
One shipment object created against the order
Documents checked against the order before it moves
Carrier, service and mode chosen by rule
Label and AWB generated in a single step
AWB and tracking written back automatically
✦Agentic Use Cases
✦

Document Verification

Extracts the attached document and matches it to the consignment

✦

Allocation Engine

Chooses carrier, service and mode against the planning rules

✦

Integration-Failure Reachouts

Chases the carrier when a booking never confirms

Shipsy

Process State | Shipment Execution & Tracking Manager

Hands the part to the carrier — and answers where it is until it is delivered

Stops being the tracking system
Current State
Documents assembled and filed by hand at hand-over
Status found by opening each carrier's portal
Every carrier reports status in its own words
A slip is discovered when the customer calls
Delivery evidence left with the carrier
Future State
Documents printed from the operational interface
One standardised status across every carrier
Milestones and EDD changes notified automatically
A delay is forecast, not reported afterwards
Proof of delivery verified against the consignment
✦Agentic Use Cases
✦

Risk Radar

Forecasts the shipment that will miss its committed date

✦

Carrier Reachouts

Asks the carrier for the milestone or ETA that never arrived

✦

POD Verification

Checks signature, photo and documents against the consignment

Shipsy

Process State | Freight Payment & Settlement Manager

Validates every carrier charge and settles it in SAP

The Control Spreadsheet retires
Current State
Monthly charges arrive by email in Excel
Entry packages parked on a shared drive
Rates checked against the contract line by line
Disputes run over email
The Control Spreadsheet is the record
Future State
Contracted rates are in the system before the invoice
Every line is checked, not the ones there was time for
Disputes tracked through to closure
The settled amount posts to SAP as PR, PO and FRS
Billing accuracy visible by carrier and by DC
✦Agentic Use Cases
✦

Rate-Card Digitisation

Reads any carrier's contract format into a structured rate card

✦

Freight-Invoice Audit

Checks every line against the contracted rate

✦

Settlement & Dispute

Raises the dispute and tracks it through to the agreed amount

Shipsy

Process State | Global Control Tower Manager

Owns how all five distribution centres ship — and what happens when one slips

Run by exception, not by chasing
Current State
Five DCs on five logistics systems
Each site works to its own process
Carrier performance cannot be compared across sites
Exceptions surface locally, if at all
A network answer means asking five people
Future State
One process, configured per site rather than rebuilt
Every site works to the same process, not its own
Carriers ranked on the same measures everywhere
Exceptions raised to one queue with an owner
Reports scheduled to arrive, at DC and network level
✦Agentic Use Cases
✦

AgentFleet

Every agent in one console — task queue, activity log and the exceptions that need a human

✦

Delivery Reason Verification

Verifies the reason a carrier gives for a failed delivery

✦

Carrier Call-Back on Undelivered

Calls the carrier for a commitment on anything left undelivered

Shipsy

As-is → To-be

Process mapping & capability enhancement

Business Process
As Is
To-Be
Impact
Order Intake and Creation
  • Orders raised across SAP + Outlook
  • Three disconnected triggers, by email
  • Data re-keyed between systems
  • One order in Shipsy, synced with SAP
  • Business-line tag drives the flow
  • Softdata upload — no re-keying
  • Single source of truth
  • Faster order-to-ship
  • Fewer manual errors
Labels, AWB and Carrier Booking
  • Log into each carrier app
  • Re-type shipment; make label & AWB
  • AWB keyed again into SAP
  • Auto label & AWB, multi-carrier
  • 250+ carriers via API / EDI
  • AWB & tracking written to SAP
  • No double data-entry
  • Faster dispatch
  • No transcription errors
Trade and Export Compliance
  • HTS / COO / AES filed by hand
  • Bill-to / Ship-to checked by hand
  • Paper docs stapled & archived
  • Compliance built into the flow (OGTM)
  • AI document verification
  • Fewer customs holds
  • Audit-ready traceability
  • Export risk controlled
Tracking and Visibility
  • Track on each carrier website
  • Chase by phone & email
  • No cross-DC view
  • Real-time milestones, all carriers
  • Control Tower across five DCs
  • Risk Radar flags slips
  • One live view of every shipment
  • Proactive exception handling
  • Consistent status
Freight Audit and Settlement
  • Monthly charges in Excel
  • Rates validated line by line
  • Disputes over email
  • AI audit vs contracted rates
  • Auto dispute & settle; FRS to SAP
  • Stops billing leakage
  • Frees finance effort
  • Faster settlement
Exception and Carrier Performance
  • Reactive, manual chasing
  • No carrier-performance view
  • Issues surface late
  • AI auto-chases carriers (Risk Radar)
  • Alerts on delays / misses
  • Proactive operations
  • Measurable carrier SLAs
  • Fewer SLA breaches
Shipsy

Why Shipsy

Shipsy partnership
differentiators

  • One platform

    SAP + tracking + freight audit + compliance

  • Full AWB-to-SAP traceability

    Every part, every PO

  • Extensive carrier integration

    Including Embraer’s suppliers

  • Best-in-class process value chain

    Built to optimise critical inventory

  • AI-native platform

    Ready for what comes next

  • Outcome-based delivery approach

    Our goals aligned with your KPIs — a partner in outcomes

  • Proven at enterprise scale

    250+ customers · 5B+ shipments

Shipsy
05

Integration & Architecture

Where Shipsy sits in Embraer’s system landscape, and how it connects to SAP, OGTM and the operator network.

05
Shipsy
1 · Landscape

New landscape (with Shipsy)

Between the order in SAP and the carrier sits a manual layer — courier portals, five DC-local ways of working, spreadsheets and paper. That layer becomes one execution platform.

System of record

SAP ECC

Orders, PO, part & serial, commercial invoice and Nota Fiscal flow in — AWB, tracking, cost and documents are written back against them.

Trade compliance

Trade Management System

OGTM owns HTS, country of origin, licences and the ITN. The booking is gated on its decision.

→
Today’s manual layer
Courier portalslog in per carrier, re-type, print the label
Five DC-local ways of workinga different tool and process per DC
Spreadsheets & e-mailtracking, chasing, EDD updates
Manual freight-invoice checksrates verified line by line in Excel
Paper document setprint, sign, photocopy, archive bin
→
Shipsy
Order & shipment intake Document verification Compliance gate Allocation engine Label & AWB Pickup booking Milestone tracking & ePOD Notifications Freight-invoice audit Settlement & consolidated invoicing Control tower & BI AI agents — embedded in every step
→
Carrier network

Carriers & partners

Operators and vendors connect through one integration layer, in whichever format their own systems support.

One execution layer across all five DCs — one shipment record, one set of milestones, one audit trail, and freight cost checked before it is paid.
Shipsy
2 · Architecture

Integration architecture — systems & data flows

EMBRAER — ENTERPRISE SYSTEMS SAP ECC orders · parts · commercial invoice · S/4HANA 2028 Trade Management System OGTM — HTS, COO, licence, ITN Salesforce shipment status for customer-facing teams — to confirm Orders, parts & invoice ↓ AWB, tracking & POD ↑ REST API · file Shipment & part data ↑ Clearance, HTS & ITN ↓ API / file AWB & tracking number ↑ Delivery status, EDD revised/missed ↑ Webhook · API INTEGRATION LAYER  ·  REST API  ·  WEBHOOK  ·  FILE / SFTP  ·  EDI  ·  EMAIL & DOCUMENT CAPTURE EXECUTION PLATFORM Order intake Compliance gate Booking Label & AWB Tracking & ePOD Freight audit Control tower AI Agents API · EDI · SFTP Booking, label & AWB ↓ Milestones, POD & invoice ↑ API · CSV Pickup instruction ↓ ASN ↑ Logistics operators FedEx · DHL · DSV / DB Schenker · Kuehne+Nagel & others Vendors & suppliers inbound & repair-return legs LOGISTICS OPERATORS & VENDORS arrows show direction  ·  data objects & method shown per link  ·  exact field mapping confirmed in the technical blueprinting session
Division of ownership: SAP owns the commercial and fiscal record · OGTM owns the compliance decision and gates the booking · Shipsy owns logistics execution — and writes the AWB, tracking, cost and documents back.
Flexible by design: every link above is a choice, not a requirement — REST API, webhook, EDI, scheduled file or e-mail capture — and a partner can move between them later without a change inside Embraer.
Shipsy
Appendix

Security & Compliance

Platform certifications, user access control and approval governance.

ShipsyPlatform compliance and certifications — GDPR, SOC 1/2, ISO 27001, VAPT, PII encryption, multi-cloud, SSO, open APIs, RBAC
ShipsyUser access security — PII data encryption, application access, security configurations, database and code access
ShipsyAccess management — RBAC model, account activation with email verification, two-level authentication
ShipsyRole Based Access Management — permissions and data visibility by area of operation
ShipsyApproval Based Flows — actions gated by rules defined in the system
Shipsy
06

Q&A & Next Steps

Open discussion, and how we align on the path forward.

06

1 / 14p3 Aug
← → to move · G for all slides · F for fullscreen

All slides click to jump · Esc to close