automation.engineer
All case studies

Ever Blooming Originals / Project case study

2021Recorded work

Ever Blooming Originals.
Production time,
captured per product.

At Ever Blooming Originals, two barcode scans marked the start and finish of production. The timer connected those events to calculate time per product; later versions recorded elapsed minutes in a spreadsheet.

Client
Ever Blooming Originals
Contribution
First-person build and device setup guidance
Project status
Timer implementation & handover

Tools & working context

Project scope and implementation.

  • Make/Integromat mobile app
  • barcode scanning
  • datastore
  • Google Sheets

01 / Business context

The problem
to solve.

Ever Blooming Originals needed to track the time taken to produce each product. Production-time capture needs a simple interaction at the point of work. Requiring someone to open a spreadsheet and type a start and end time adds a different task to the process being measured.

The worker scanned the same barcode to start and finish the job. The system saved the start time between those scans.

Inside the workflow

A closer look
at the handoffs.

Start with the main path and its branches. Select a step for context, or switch to the technical map for implementation detail.

  • Worker scans barcode
    Each mobile scan supplies the production barcode to the timer.
  • Running-timer datastore
    Look up whether this barcode already has a stored start timestamp.
  • No timer: store start
    Save the current timestamp and wait for the worker’s next scan.
  • Timer found: calculate interval
    Compare the new scan time with the stored start to calculate elapsed minutes.
  • Record elapsed minutes
    The later version writes the completed interval into Google Sheets.
  • Clear active timer
    Remove the running record after the completed interval is recorded.
Read the workflow notes
  1. 01 / Start

    Create the running timer

    A mobile scan supplied a barcode. When no running entry existed for that code, the scenario stored a start timestamp against it.

  2. 02 / Finish

    Calculate the elapsed time

    The next scan retrieved the stored start, calculated the interval in minutes and cleared the running timer so the code could be used again.

  3. 03 / Record

    Connect the result to a working sheet

    Later versions mapped the output to Google Sheets. Handover recordings explained separate employee/device scenario templates for Android and Apple connections.

This production-timing system was built for Ever Blooming Originals.

03 / Implementation detail

How it
was built.

A saved start time told the system whether a scan began or finished the job. After recording the completed interval, it cleared that start so the code could be used again.

The build included formula fixes and an early version without the spreadsheet connection. Later walkthroughs show the reporting connection, but do not confirm setup and use on every employee’s device.

Barcode-to-SKU resolution remained a separate decision. The record does not support a live Etsy product lookup, payroll calculation or labor-cost accounting integration.

04 / Outcome & scope

Result
and scope.

The build combined a two-scan timer, configured spreadsheet output and instructions for setting up employee devices.

The implementation covered the timer workflow and its handover; shop-wide rollout and operational measurement were separate stages.