Logo Light

How to Build an Order Quick View

Aug 27, 2026

Every order table eventually runs into the same annoyance — you're looking at an order, and the only thing it tells you is a customer's name. Their phone number, their address, how long it's been since they last ordered — all of that lives on a completely different table, one click and one search away every single time.

In this tutorial, we'll build an Order Quick View — an Order table that pulls a customer's contact details directly onto each order using Lookup, and calculates how long it's been since their last purchase using Custom Logic. Everything you need, on the row you're already looking at.

Why this matters

Data being technically stored somewhere isn't the same as data being usable. A phone number sitting on a separate Customer record might as well not exist if you have to leave the order you're working on just to find it.


Table Columns

Here's what we're working with — a Customer table with Name, Phone, and Address, linked to an Order table with Order Date and Amount, connected through a One-to-Many relationship.

  • Customer — Name, Phone, Address
  • Order — Customer (linked), Order Date, Amount
CustomerOrder
1.customer-order-table-columns.png1.customer-order-table-columns.pngCustomer and Order table columns showing the One-to-Many link between themCustomer and Order table columns showing the One-to-Many link between them

Step 1: Add Your Customers and Orders

Add a few customers, then log a few orders for each, linking every order back to the customer who placed it.

Customer table populated with sample records for Ethan Walsh and Grace OdomCustomer table populated with sample records for Ethan Walsh and Grace Odom

Order table showing multiple order records linked to each customerOrder table showing multiple order records linked to each customer

For this walkthrough, assume today is August 26, 2026, with the following orders:

  • Ethan Walsh — phone (555) 201-4487, orders on July 2 and August 20, 2026
  • Grace Odom — phone (555) 887-3021, orders on May 14 and June 1, 2026

Right now, opening an order only tells you which customer it belongs to by name. Everything else about that customer is one search away.


Step 2: Pull Contact Details with Lookup

On the Order table, add a new column and set its type to Lookup.

Adding a new Lookup column on the Order table for the customer's PhoneAdding a new Lookup column on the Order table for the customer's Phone

Point it at the linked Customer relationship, and select the Phone field to pull.

Configuring the Lookup field to pull Phone from the linked Customer recordConfiguring the Lookup field to pull Phone from the linked Customer record

Repeat the same process for Address.

Configuring a second Lookup field to pull Address from the linked Customer recordConfiguring a second Lookup field to pull Address from the linked Customer record

Save both, and every order fills in instantly with its customer's contact details:

  • Ethan Walsh's orders → phone and address appear automatically
  • Grace Odom's orders → phone and address appear automatically

Order table showing Phone and Address columns automatically filled in from the linked CustomerOrder table showing Phone and Address columns automatically filled in from the linked Customer

What just happened under the hood

Because each order links to exactly one customer, this is a textbook case for Lookup rather than Rollup — there's no aggregation happening, just a direct pull of a single linked value. Update Ethan's phone number once on his Customer record, and every one of his past and future orders reflects it immediately, with nothing duplicated anywhere.


Step 3: Calculate Days Since Last Order

Contact details are pulled in, but there's still a useful question this table can't answer yet — how long has it been since this customer last ordered? Add a new column and set its type to Custom Logic.

Adding a new Custom Logic column for Days Since Last OrderAdding a new Custom Logic column for Days Since Last Order

Describe what you want — calculate the number of days between this order's Order Date and today.

Describing the logic to calculate days between Order Date and todayDescribing the logic to calculate days between Order Date and today

Confirm the clarification screen, checking that it's measuring against today's date, not a fixed reference point.

Clarification screen confirming the calculation measures days from Order Date to todayClarification screen confirming the calculation measures days from Order Date to today

Save it, and the field calculates instantly for every row:

  • Ethan Walsh's July 2 order → 55 days
  • Ethan Walsh's August 20 order → 6 days
  • Grace Odom's May 14 order → 104 days
  • Grace Odom's June 1 order → 86 days

Order table showing Days Since Order calculated for every rowOrder table showing Days Since Order calculated for every row

What just happened under the hood

Because this calculation compares a stored date against today's constantly moving date, Ambisius runs it as an on-demand calculation — it's never stored, and recalculates live every time you open the table. Come back tomorrow, and every number here has quietly moved forward by one, without anyone touching a single row.


Step 4: See It All Come Together

Open Ethan Walsh's August 20 order. Without navigating anywhere else, you can already see his phone number, his address, and that his last order before this one was 55 days prior — all sitting on the row you're already looking at.

A single order row showing Phone, Address, and Days Since Order all visible without leaving the tableA single order row showing Phone, Address, and Days Since Order all visible without leaving the table

Now update Ethan's phone number on the Customer table, changing it to a new number.

Updating Ethan Walsh's phone number on the Customer tableUpdating Ethan Walsh's phone number on the Customer table

Both of his orders reflect the new number instantly.

Ethan Walsh's orders change from (555) 201-4487 → (555) 209-9902, everywhere at once.

Both of Ethan Walsh's order records showing the updated phone number automaticallyBoth of Ethan Walsh's order records showing the updated phone number automatically

What this replaces

Without Lookup, this same information would either need to be manually copied onto every order — creating stale, duplicated data the moment a customer updates their number — or require leaving the Order table entirely to check the Customer record. Here, it's neither duplicated nor hidden away; it's just there, and it's always current.


Step 5: Build a View for Recently Active Customers

Create a new view, sort by Days Since Order ascending, and save it as "Recent Orders First."

Saved view named Recent Orders First sorted by Days Since Order in ascending orderSaved view named Recent Orders First sorted by Days Since Order in ascending order

Now the freshest orders always float to the top, with no manual sorting required each time you check.

The wow moment

This view doesn't need re-sorting tomorrow. Since Days Since Order recalculates live every day, the ordering itself stays correct without you lifting a finger — today's newest order is at the top today, and next week's newest order will be at the top then, automatically.


Recap

  1. A Customer table linked to an Order table via One-to-Many
  2. Two Lookup fields pulling Phone and Address directly onto each order
  3. A Custom Logic field calculating Days Since Order, live against today's date
  4. A demonstration of a phone number update reflecting instantly across every linked order
  5. A sorted view keeping the most recent orders always at the top
What you had beforeWhat you have now
Leaving the order to look up a customer's phone numberContact details visible directly on the order
Manually copying customer info onto every orderOne linked value, reused everywhere, never duplicated
No sense of how recent or stale an order relationship isA live "days since" field, always accurate

This same combination — Lookup for direct details, Custom Logic for anything time-sensitive — applies well beyond orders. Support tickets pulling customer tier, appointments pulling client history, or invoices pulling billing details can all be built the same way.

Try it yourself

This exact setup is available as a ready-made template. Duplicate it, explore it live, and make it yours in a few clicks.

Try the Live Preview

On this page

Related articles

Explore more product articles and best practices for teams building with Ambisius.

Still Using Spreadsheets?
You Should Try This.

Turn familiar spreadsheets into a structured system built for your business

Try Ambisius for Free

No commitment. No credit card required.

Logo Light

© 2026 Ambisius. All rights reserved.