Flow for Lightspeed Retail is coming soon. Join early access
Blog · Data relationships

Use related POS data in reports, updates and deletions

Use connected Epos Now information so a report or bulk change includes useful business details held elsewhere in the POS.

Flow + MorphPublished 2 December 2024Built from practical POS experience
Flow + MorphPublished 2 December 2024

Use connected Epos Now information so a report or bulk change includes useful business details held elsewhere in the POS.

What related data means

A transaction contains a customer ID, product IDs, a location and a staff member, but not every useful field from those records. Related-data support lets Slynk follow those connections and work with the customer name, product supplier, location details or staff role without asking you to combine separate spreadsheets.

Use it with Flow

Flow uses related data to create richer exports, reports, feeds and alerts. A transaction report can include customer, product, supplier and location fields in one row instead of returning IDs that someone must look up later.

  • Export customers who bought from selected brands or categories
  • Send sales with product, supplier and location details
  • Send alerts using information from connected records

Use it with Morph

Morph uses the same relationships to target and change the right records. It can start with recent sales, identify the connected products or customers and preview an update before applying it.

  • Hide out-of-stock products from the till
  • Change customer types using purchase behaviour
  • Archive products connected to an inactive supplier

Put this capability to work.

Start from the closest template or tell us what you want to achieve.