Airtable Food Traceability Database

Job ID: 40087374

Budget: $30 – $250 AUD

We are a food manufacturing business and need an Airtable setup built to track batch traceability from raw materials through to finished goods and dispatched customer orders.

This is not accounting or costing related. We do not need P&L, COGS, invoicing, or financial reporting.

Our main challenge is traceability, especially with Shopify bundles (where one Shopify product contains multiple underlying products).

What we need built in Airtable:

A relational Airtable base with the following core components:

Batches table

Batch / Lot ID

Product type

Production date

Quantity produced

Quantity remaining

Notes

Products table

Individual products

Bundle products

Bundle breakdown (components + quantities)

Link products to batches

Orders table

Shopify order number

Order date

Customer name

Products ordered (including bundles)

Fulfilment status

Fulfilments / Dispatch table

Linked to Orders

Linked to Batches

Product/component

Quantity dispatched

Dispatch date

Ability to trace batch → order and order → batch

Key requirements:

Must handle bundles properly (bundle = multiple components, each with its own batch)

Clear traceability reports (e.g. “which orders used batch X?”)

Simple UI/views for packing staff to assign batch numbers during fulfilment

Prefer Airtable Forms for fulfilment entry if appropriate

Clean, documented setup so we can maintain it internally

Nice to have (but not mandatory):

Ability to import Shopify orders via CSV

Simple dashboard or views for batch history and dispatch records

Basic guidance or short handover on how to use it

What we will provide:

Example Shopify order exports

List of products and bundle compositions

How our fulfilment process works in practice

Ideal freelancer:

Strong Airtable experience

Comfortable building relational databases (not just flat spreadsheets)

Experience with inventory, manufacturing, or traceability systems is a big plus

Clear communicator

Deliverables:

Fully functional Airtable base

Explanation of table relationships

Any recommended best practices for ongoing use