Supply Chain & Manufacturing

Zero-ETL graph analytics for supply chain and manufacturing.

Connect materials, production batches, facilities, and orders through graph queries over your existing data. Trace where a batch came from and explore what depends on it, without loading a separate graph database.

MATERIALSPRODUCTIONDELIVERYLot ASupplier ALot BSupplier BBatchProduction facilityShipment 01Shipment 02PuppyGraphExisting supply chain & manufacturing dataMaterials · Batches · Facilities · ShipmentsMATERIALSPRODUCTIONDELIVERYLot ASupplier ALot BSupplier BBatchProductionfacilityShipment 01Shipment 02PuppyGraphExisting supply chain &manufacturing dataMaterials · Batches ·Facilities · Shipments

01 / Graph analytics for supply chain & manufacturing

Follow connections from suppliers through production to delivery.

Start with a supplier, a shipment, or an order. Follow connected records to understand dependencies, trace origins, and bring context to operational decisions.

Examples use simplified graph models. Adapt labels and properties to your schema.

01

Supplier & material dependencies

Find products that depend on the same upstream supplier. Follow sourcing relationships across the tiers represented in your data, connecting suppliers to components and the products that use them.

SupplierUpstreamSupplier ADirectSupplier BDirectComponent ASupplied partComponent BSupplied partProduct AUses partProduct BUses partSupplierUpstreamSupplier ADirectSupplier BDirectComponent ASupplied partComponent BSupplied partProduct AUses partProduct BUses part
View Cypher example

Set $supplierId to the upstream supplier. SUPPLIES runs from an upstream supplier to its downstream customer; this example follows up to three supplier links.

MATCH path = (upstream:Supplier)-[:SUPPLIES*1..3]->(direct:Supplier)
             -[:SUPPLIES_COMPONENT]->(part:Component)
             <-[:USES_COMPONENT]-(product:Product)
WHERE upstream.id = $supplierId
RETURN DISTINCT product.id AS product,
       part.id AS component, path
LIMIT 25

Returns: Products and components that depend on the selected supplier, with the recorded supply path for each result.

02

Production genealogy & traceability

Trace a shipment back through production batches and parent lots to identify its source lots and facilities. Follow recorded lineage forward to find other shipments linked to the same material or production event.

ShipmentStarting pointBatchShipped batchLot ASource lotLot BSource lotcontainsShipmentStarting pointBatchShipped batchLot ASource lotLot BSource lotcontains
View Cypher example

Set $shipmentId to the shipment. HAS_PARENT points upstream. A source lot here means a lot with no recorded parent; the search is bounded to two parent-lot links.

MATCH (shipment:Shipment)-[:CONTAINS]->(:Batch)
      -[:FROM_LOT]->(lot:Lot)
MATCH lineage = (lot)-[:HAS_PARENT*0..2]->(source:Lot)
MATCH (source)-[:PRODUCED_AT]->(facility:Facility)
WHERE shipment.id = $shipmentId
  AND NOT (source)-[:HAS_PARENT]->()
RETURN facility.id AS facility, lineage
LIMIT 25

Returns: Recorded source facilities and the lot paths connecting them to the shipped batch. Source lots beyond two parent-lot links are outside this example.

03

Inventory & fulfillment

Find inventory locations holding the products needed for an order. Connect orders to products and stock records, then inspect quantities and delivery timing to evaluate fulfillment or replenishment options.

OrderDemandProductRequiredLocation AStock recordLocation BStock recordcontainsOrderDemandProductRequiredLocation AStock recordLocation BStock recordcontains
View Cypher example

Set $orderId to the order. CONTAINS carries requested quantity; STOCKS carries recorded quantity and availability date.

MATCH (order:Order)-[need:CONTAINS]->(product:Product)
      <-[stock:STOCKS]-(location:Location)
WHERE order.id = $orderId
RETURN product.id AS product, need.quantity AS requested,
       location.id AS location, stock.quantity AS recordedStock,
       stock.availableOn AS availableOn
ORDER BY product, location
LIMIT 25

Returns: Up to 25 product/location options with quantities and dates for review. The query does not allocate stock or account for reservations.

02 / Graph analytics on supply chain & manufacturing data

Run graph analytics on your operational data.

Your tables already record materials, production batches, facilities, and orders. Map those records and their relationships into a graph model, then trace origins and dependencies with PuppyGraph.

Traditional approach

Copy data. Keep two systems in sync.

ETL + duplicate storage + ongoing sync

  1. Curated operational tables
    IcebergBigQueryDatabricksPostgreSQL
  2. Build and run a graph-loading pipeline
    ExportTransformLoad
    Export, transform, load, then synchronize changes
  3. Operate a separate graph databaseStore and maintain another copy of the data
    Keep the graph copy in sync
  4. Supply chain & manufacturing analytics
  • More pipeline work. Propagate updates, backfills, and schema changes into the graph copy.
  • Another system to operate. Manage graph storage and the synchronization jobs alongside your data platform.

With PuppyGraph

Query existing data. Skip the graph copy.

Zero-ETL · Query data in place

  1. Curated operational tables
    IcebergBigQueryDatabricksPostgreSQL
  2. PuppyGraph queries source tablesMap tables to vertices and edges in a graph schema
  3. Supply chain & manufacturing analytics
  • No graph-loading pipeline. Query your existing operational tables through the graph model.
  • No separate graph data store. Keep your source data in the platform you already operate.

03 / Traceability in practice

Trace a shipment back to its origins.

Follow a shipped batch through its production lineage to find source facilities and the paths that connect them. This example adapts a real traceability question using synthetic data.

Shipment S01Contains batch B24Lot L30Production lotLot L10Source lotLot L20Parent lotLot L05Source lotFacility ARecorded sourceFacility BRecorded sourceparent lotsShipment S01Contains batch B24Lot L30Production lotLot L10Source lotLot L20Parent lotLot L05Source lotFacility ARecorded sourceFacility BRecorded sourceparent lots
Arrows trace upstream. The sample ends at L10 and L05, within two parent-lot links of L30; deeper history is outside this example.

From shipment to source

Find the facilities behind shipment S01.

  1. Identify B24, the batch listed on shipment S01, and L30, its linked production lot in this example.
  2. Follow L30’s parent lots along both branches: directly to L10, and through L20 to L05.
  3. Return the facilities recorded for those source lots, keeping each lineage path with the result.
Source facilities for shipment S01
FacilityLineage from lot L30
Facility AL30 → L10
Facility BL30 → L20 → L05

Review each source facility alongside the recorded lot relationships that connect it to the shipment.

Build your supply chain graph

Bring graph context to supply chain and manufacturing workflows.

Download PuppyGraph to query your operational data, book a demo for your use case, or join our Slack community to ask questions.

$ docker run -p 8081:8081 \
  -p 8182:8182 -p 7687:7687 \
  puppygraph/puppygraph:latestPulling puppygraph/puppygraph:latestStarting PuppyGraphWeb console listening on 0.0.0.0:8081Gremlin endpoint listening on 0.0.0.0:8182PuppyGraph is running# no pipelines · no second database · no data movement