Skip to content
All integrations Integration / Made by Fressko

Stock sync and order tagging.

Made by Fressko sells through more than one Shopify store: Australia and the rest of the world on one, the United States on another, and wholesale alongside. Every store sells the same cups, and a good number of those cups are personalised or made to order.

Store case study
  1. 01

    Shopify stores

    Each store’s inventory levels, and the webhook that fires whenever one changes.

  2. 02

    Hydra

    Plutocracy’s inventory sync app, modified for Fressko. It links stores into a group and carries each change across the others.

  3. 03

    AWS

    EventBridge receives the webhooks and Lambda processes them, in Sydney.

  4. 04

    PostgreSQL

    Store groups, location mappings and the movement log.

  5. 05

    Angular storefront

    Writes personalisation, preorder and bundle details onto every cart line.

The objective

What it
had to do.

Shopify stores do not know about each other. A cup sold in one is still on the shelf in the next until something tells it otherwise. And an order for an engraved cup on preorder looks, from the orders list, exactly like any other. The stock side runs on Hydra, an inventory sync app, modified for the way Fressko’s stores are set up.

Business objectives

  • Keep available stock in step across every store that sells the same SKU
  • Do it as the change happens, rather than on a nightly schedule
  • Leave a record of every adjustment, so a number that looks wrong can be traced back to where it came from
  • Have personalised, preorder and bundled orders identify themselves, rather than relying on someone opening each one

The stack

  • Shopify
  • Hydra
  • AWS Lambda
  • Amazon EventBridge
  • PostgreSQL
  • Angular

Key flows

How it runs.

3 flows

Flow 01

A stock change, carried across

Hydra links the stores into a group. A change in any one of them is applied to the rest, matched by SKU.

  1. 01 Shopify

    An inventory level changes in one store and Shopify sends an inventory update webhook.

  2. 02 AWS

    The event lands on an EventBridge bus and a Lambda function picks it up.

  3. 03 Hydra

    The store’s group is looked up, and the SKU is resolved from the inventory item.

  4. 04 Hydra

    For each linked store, the location is translated through the group’s location mapping and the variant with the same SKU is found.

  5. 05 Hydra

    If the other store already holds a newer change, or there is no difference, it is left alone.

  6. 06 Shopify

    Otherwise the difference is applied to that store’s available stock as an adjustment.

  7. 07 PostgreSQL

    The movement is written to a log the team can read inside Hydra.

Flow 02

Stocktake across the group

When a count needs correcting, it is corrected in one place.

  1. 01 Hydra

    The stocktake screen reads one SKU’s levels across every store in the group, side by side.

  2. 02 Hydra

    The team sets the level from that screen, rather than opening each store’s admin in turn.

Flow 03

Orders that describe themselves

What makes an order different is written onto it at the moment it is added to cart, so it is there to act on when the order lands.

  1. 01 Storefront

    A personalised line carries its own specification: font, size, monogram or stamp, and position on the cup.

  2. 02 Storefront

    Preorder and backorder lines are marked as such, with the message the customer was shown.

  3. 03 Storefront

    Bundle, gift-with-purchase and free gift lines are marked, so they can be told apart from the same product bought on its own.

  4. 04 Shopify

    All of it arrives on the order as line item properties.

  5. 05 Shopify

    Custom tagging workflows then tag the order, so it can be filtered and handled by type from the orders list.

More integrations.

All integrations

Your systems, connected

What does your
store not talk to?

Tell us which systems you run and where the re-keying happens. We’ll come back within one business day with where we would start.

Start a project