Skip to content
Gravity Tables

📦 Inventory tracking

Inventory that updates from the warehouse floor.

Whoever picks the box updates the count. The table on the website reflects reality, not a Friday-evening recount.

The before

What this replaces, specifically.

Stock counts wrong by Tuesday

Counted Monday morning. By Tuesday, three orders shipped and the spreadsheet says we still have them.

Field staff don't use the ERP

It's a desktop app. They have phones. The count never gets updated.

Reorder triggers fire too late

By the time the count drops below threshold, you've been out of stock for a week.

The after

What Gravity Tables does instead.

Mobile card layout for field updates

On a phone, the table becomes editable cards. Tap "Quantity", type the new number, save.

Conditional formatting on stock levels

Cells under threshold turn red. Visual scan of the table = visual scan of the warehouse.

Webhook on edit

Edit a quantity, fire a webhook. Slack notification, reorder workflow, anything.

The shortcode

Copy. Paste. Customize the IDs.

This is the actual shortcode pattern this use case uses. Drop it on a page, change the form ID, you're shipping.

page-template.php
[gravity_table id="stock" allow_edit="quantity" mobile_layout="cards" webhook_on_edit="https://hooks.slack.com/..."]

Real scenario

A multi-location retailer

Before

  • Friday-evening stock counts
  • WhatsApp messages from store managers with corrections
  • Reorder triggers fire from outdated data

After

  • Each manager's phone shows their store's table
  • Tap to update, table refreshes for HQ
  • Reorder triggers fire on the live count
"We were two purchase-orders away from a Netsuite implementation. Gravity Tables saved us $40k of consulting."
Rachel T., retail ops

Ready when you are

Stop exporting CSVs. Start shipping dashboards.

10 days of full Pro access. If it doesn't pay for itself in the first week, you don't have to keep it.