Customer stories

Customer story•Integration

From customer request to production in seven days.

A leading EdTech platform wanted shipment tracking inside its own product. Symplichain delivered it through one integration, and the account converted to paid. The customer is described here and is not named, pending their approval.

The challenge

A tracking capability they did not want to build themselves.

The platform wanted logistics tracking inside its own product, so that its teams would not switch to a separate tool. Building it in-house meant carrier integrations, document handling and a lasting support burden outside its core product. Embedding another company’s tracking works only on three conditions.

  1. 01

    It has to be fast

    The request came with a date attached, so a long integration project was not an option.

  2. 02

    It has to reach every surface

    The capability had to appear where their users already work: in their backend, in a mobile app for field users and in a web console.

  3. 03

    The data has to stand on its own

    The data had to be good enough to show to an end customer without a disclaimer beside it.

The approach

One integration, every surface.

Symplichain exposes tracking as an API first, so a single shipment record drives every surface. Nothing had to be modelled twice, and nothing was built specially for this customer.

  • A REST API for their backend, with webhooks on status change, so nothing has to poll.
  • An Android surface for field users that reads the same shipment records.
  • A web console for their operations team, with no separate data setup.
  • Permission-aware access, so each account sees only its own shipments.

How it went

Four moves in one week.

No new platform capability was built for this engagement. The speed came from an integration surface that already existed.

  1. 01

    Scope

    The request was checked against what the platform already offered. Every item on the list mapped to an existing capability.

  2. 02

    Connect

    Keys were issued, endpoints were wired into their backend, webhooks were subscribed and test shipments ran from end to end.

  3. 03

    Extend to surfaces

    The Android and web surfaces were pointed at the same records and reviewed with their team before release.

  4. 04

    Cut over

    The integration was promoted to production and began carrying real shipments for their users.

The outcome

In production in seven days, then a paid account.

The integration reached production seven days after the request, and the account converted to paid. It also showed that the platform did the work, and a bespoke project team was not needed.

from request to production
7 days
paid conversion
1
  • Web, Android and API surfaces shipped from a single integration.
  • The account moved from a feature request to a paid engagement.
  • No platform capability had to be built specially for this customer.

The platform behind it

The products behind this integration.

SymConnect™ provides the REST API and webhooks in this story, and SymTrust™ makes sure each account sees only its own records.

Bring us the request with a date attached.

Tell us what your product needs and by when. We will check it against what the platform already offers.