Technology

Sage green and peach graphic: a reorder checklist (cover, trend, lead time, order) beside the Runway inventory table, GrtLabs logo
Deciding What to Reorder on BigCommerce: A Simple Method
Deciding What to Reorder on BigCommerce: A Simple Method 1024 538 Nadeem Shaikh

To decide what to reorder on BigCommerce, compare each product’s days of cover with how long your supplier takes to deliver, check whether sales are rising or falling over 30, 60 and 90 days, and then size the order to cover lead time plus the period you want to stock for. The data points you to the products that need attention; you make the final call based on cash, space and plans.

This guide gives you a four-step method you can run in about 20 minutes a week.

Why a simple method helps

Guessing works until it doesn’t. Order too little and a best seller runs out, which can cost sales. Order too much and cash sits on the shelf. A repeatable method keeps you out of both traps without needing a complex system.

The four-step method

Step 1: Check days of cover

Days of cover = stock on hand ÷ average daily sales (from the last 30 days). It tells you roughly how many days your stock will last. Sort products from lowest to highest. The top of the list is where to start. (Our low stock guide covers how to set a threshold.) (More detail in our days of cover guide.)

Step 2: Compare with lead time

Lead time is the number of days from placing a purchase order to having stock ready to sell. If a product’s days of cover is close to or below its lead time, new stock may not arrive before it runs out.

Add a buffer (safety stock) for delays or busy weeks. A simple rule many small stores use:

Look closely when days of cover < lead time + buffer

Step 3: Check the trend

Compare units sold over 30, 60 and 90 days (see how to build an inventory report with those columns):

  • Speeding up: the last 30 days is more than a third of the 90-day total. You may want a bit more.
  • Steady: roughly a third each month.
  • Slowing down: the last 30 days is less than a third of the 90-day total. You may want a bit less, or wait.

Also think about anything the numbers cannot see: an upcoming promotion, a holiday, or a product you plan to discontinue.

Step 4: Size the order

A plain-terms way to estimate quantity:

Order quantity ≈ (average daily sales × days you want to cover) − stock on hand

“Days you want to cover” is usually lead time plus how long you want the new stock to last, plus your buffer. Round to your supplier’s case or minimum order size.

A worked example (made-up numbers)

These numbers are an example only.

Your mug supplier takes 10 days to deliver. You want a 5-day buffer and you order roughly once a month (30 days).

Product On hand Sold 30d Sold 90d Avg daily Days of cover
Ceramic mug 20 60 140 2.0 10
Wool scarf 45 30 60 1.0 45

Mug:

  1. Days of cover: 10.
  2. Lead time + buffer: 10 + 5 = 15. Cover is below that, so it needs attention.
  3. Trend: 60 of 140 sold in the last 30 days, more than a third. Sales are picking up.
  4. Size: days to cover = 10 (lead) + 30 (cycle) + 5 (buffer) = 45. Average daily 2.0 × 45 = 90. Minus 20 on hand = about 70 units. If the mug comes in cases of 24, you might choose 72.

Scarf:

  1. Days of cover: 45.
  2. Well above 15, so no rush.
  3. Trend: 30 of 60 in the last 30 days, also rising, but stock is healthy.
  4. You could leave it this week and check again next week.

These are your decisions to make. If cash is tight, you might order 48 mugs now and more later. If a big sale is coming, you might order more. The math is a starting point, not a rule.

Common mistakes to avoid

  • Ignoring stockout days. If a product was out of stock for part of the month, its sales look lower than real demand.
  • Treating no sales as no need. A blank days of cover (no sales in 30 days) means not enough data, not endless stock. Check 60 and 90-day sales.
  • Forgetting minimums. Supplier minimums and case sizes often decide the final number.
  • Checking too rarely. A weekly look catches problems while there is still time to act.

Getting the numbers without a spreadsheet

You can run this method from exported orders and products in a spreadsheet. If you would rather have the numbers ready, Runway is a free, read-only BigCommerce app from GrtLabs. It shows units sold in the last 30, 60 and 90 days, stock on hand and days of cover for each product, with the products that run out soonest at the top. You can filter to low cover or out of stock, open a product in your BigCommerce admin, and download the list as a CSV to work out quantities with your own lead times. It is on the BigCommerce App Marketplace.

To be clear about what it does not do: Runway does not tell you how much to order, create purchase orders, email suppliers or change your stock. It shows the data; you decide and place the order yourself. If you need a tool shaped around your own buying process, our team builds custom BigCommerce apps and integrations.

Quick recap

  1. Sort by days of cover.
  2. Compare with lead time plus a buffer.
  3. Check the 30/60/90-day trend.
  4. Size the order, then adjust for cash, case sizes and plans.

FAQ

How do I know when to reorder a product?

Compare its days of cover with your supplier lead time plus a buffer. If cover is close to or below that number, the product needs attention now.

How much should I reorder?

A simple estimate is average daily sales times the number of days you want to cover, minus stock on hand. Then adjust for case sizes, minimums, cash and upcoming events.

What is lead time?

Lead time is the number of days between placing an order with your supplier and having that stock ready to sell.

What is safety stock?

Safety stock is extra stock, often expressed as a few extra days of sales, kept to cover supplier delays or sudden jumps in demand.

Does Runway create purchase orders?

No. Runway is a free, read-only BigCommerce app. It shows units sold, stock on hand and days of cover, and exports a CSV. You decide what to order and place the purchase order yourself.

Amber and charcoal graphic: a low-stock gauge beside the Runway inventory table, GrtLabs logo
Finding Low Stock Products in BigCommerce: A Simple Guide
Finding Low Stock Products in BigCommerce: A Simple Guide 1024 538 Nadeem Shaikh

The most reliable way to find low stock products in BigCommerce is to look at days of cover (how long stock will last at recent sales pace), not just the quantity left. Pick a threshold that fits your supplier lead time, such as 14 days, and check which products fall under it. Out of stock products and products with no recent sales are worth looking at separately.

Below we explain why quantity alone can fool you, how to set a sensible threshold, and a quick weekly routine.

Why “low stock” is not just a small number

Imagine two products, each with 10 units left. One sells five a day. The other sells one a month. The first runs out in two days. The second will last most of a year. Both show “10 in stock”, but only one is really low.

That is why a fixed quantity rule (for example, “anything under 10 is low”) often flags the wrong products. It misses fast sellers with a decent count and worries you about slow sellers with a small count.

Use days of cover instead

Days of cover = stock on hand ÷ average daily sales (usually from the last 30 days). It turns every product into the same unit: days. A product with 7 days of cover is closer to running out than one with 40, no matter what the raw counts are. Our days of cover guide walks through the formula in detail.

Setting your low stock threshold

Your threshold should be at least as long as it takes to get more stock, plus a buffer.

  • Lead time: how many days from placing an order with your supplier until the stock is ready to sell.
  • Safety stock / buffer: extra days to cover delays or a sudden jump in sales.

Threshold ≈ lead time + buffer

A common starting point is about two weeks. Runway, for example, marks products with under 14 days of cover as low cover. If your supplier takes three weeks, you would likely want a higher number for your own planning.

A worked example (made-up numbers)

Example numbers only, not real store data.

Your supplier usually delivers in 9 days and you like a 5-day buffer, so you watch anything under 14 days of cover.

Product On hand Sold last 30 days Days of cover Under 14 days?
Ceramic mug 20 60 10 Yes
Travel cup 6 9 20 No
Wool scarf 45 30 45 No
Linen tote 0 12 0 Out of stock
Gift card holder 12 0 blank No recent sales

What stands out:

  • The mug has 10 days of cover, below your 14-day line. It is worth a look today.
  • The travel cup has only 6 units, which looks scary, but at its slow pace that is 20 days. It is fine for now.
  • The tote is already out of stock, so it is losing sales.
  • The gift card holder has not sold in 30 days. It is not low; it may be a different problem.

You decide what to do with each one. The view just makes it obvious where to look. Once you know where to look, our guide to deciding what to reorder on BigCommerce covers the next step.

Three groups to check every week

1. Low cover

Products under your threshold. These are the ones most likely to run out before new stock arrives.

2. Out of stock

Products at zero. Check whether they are on order, discontinued, or simply forgotten.

3. No recent sales

Products that have not sold in 30 days. They are not low, but they tie up cash and shelf space. Check 60 and 90-day sales before deciding anything.

A view is not an alert

It helps to be clear about the difference:

  • A low stock view is a list you open and read. You choose when to check it.
  • An alert is something that messages you automatically.

Runway is a view. It does not send emails or messages. Many small store owners find a set weekly check (for example, Monday morning with coffee) works well, because it fits naturally into planning orders.

How to find low stock products

With a spreadsheet

  1. Export the last 30 days of orders and your product list with stock.
  2. Total units sold per SKU.
  3. Calculate days of cover: =IF(sold_30=0,"",on_hand/(sold_30/30)).
  4. Filter to days of cover under your threshold, then separately to stock of zero.

With a free app

Runway is a free, read-only BigCommerce app from GrtLabs. It shows units sold in the last 30, 60 and 90 days, stock on hand and days of cover for each product, with the products that run out soonest at the top. You can filter to low cover (under 14 days), out of stock, or no recent sales, open any product in your BigCommerce admin, and download the list as a CSV. Get it on the BigCommerce App Marketplace.

Runway only reads orders, products and inventory. It does not change your stock, create purchase orders or email suppliers. If you need a custom workflow on top of your store data, our team builds BigCommerce apps and integrations.

Quick recap

  • Judge “low” by days of cover, not raw quantity.
  • Threshold ≈ supplier lead time + buffer; 14 days is a common starting point.
  • Check low cover, out of stock and no recent sales as three separate lists.
  • A weekly habit works well with a view-based tool.

FAQ

How do I find low stock products in BigCommerce?

Compare stock on hand with recent sales. Calculate days of cover for each product and look at the ones under your threshold, plus anything at zero stock.

What counts as low stock?

It depends on how long your supplier takes to deliver. A common rule of thumb is any product whose days of cover is shorter than your lead time plus a small buffer.

Why not just use a minimum quantity?

A fixed quantity ignores sales speed. Ten units can last two days or a year depending on how fast the product sells.

Does Runway send low stock emails?

No. Runway is a read-only view. You open it to see low cover and out of stock products; it does not send emails or messages.

What does Runway count as low cover?

Runway marks products with under 14 days of cover as low cover, where days of cover is stock on hand divided by average daily sales over the last 30 days.

Terracotta and olive graphic: a BigCommerce inventory report with 30, 60 and 90 day sales columns next to the Runway table, GrtLabs logo
How to Build a BigCommerce Inventory Report (Units Sold Over 30, 60 and 90 Days)
How to Build a BigCommerce Inventory Report (Units Sold Over 30, 60 and 90 Days) 1024 538 Nadeem Shaikh

A useful BigCommerce inventory report puts units sold per product over the last 30, 60 and 90 days right next to current stock on hand. You can build it yourself by combining an order export and a product export in a spreadsheet, or use a free app that shows it in one table. Seeing sales and stock together is what makes the report useful.

This guide covers what to include, how to build it step by step, and when an app saves you time.

What should an inventory report show?

Many store owners start with a stock list: product name and quantity. That tells you what you have, but not whether it is enough. A report you can act on answers two questions at once:

  1. How much do I have? (stock on hand)
  2. How fast is it selling? (units sold over recent periods)

From those two, you can work out a third: days of cover, or how long current stock will last. We explain that in detail in our days of cover guide.

Why 30, 60 and 90 days?

  • 30 days shows what is happening right now.
  • 60 days smooths out a slow or busy week.
  • 90 days shows the bigger trend and helps you spot products that are speeding up or slowing down.

If a product sold 30 units in the last 30 days but only 45 over 90 days, it is picking up speed. If it sold 10 in 30 days and 90 over 90 days, it is slowing down.

The two routes

Spreadsheet route App route
Cost Free Free (Runway) or paid tools
Time per refresh Manual, every time Opens ready to read
Flexibility Total What the app shows
Good for Small catalogs, one-off checks Regular weekly checks

Building the report with exports and a spreadsheet

Step 1: Export your orders

In your BigCommerce admin, go to Orders and export orders covering at least the last 90 days. Make sure the export includes product line items (product name or SKU, and quantity).

Step 2: Export your products

Go to Products and export your catalog with current stock levels. This gives you stock on hand for each product or SKU.

Step 3: Total units sold by period

In your spreadsheet, add a column that marks each order line by age (days since the order date). Then use a pivot table or SUMIFS to total quantity per SKU for:

  • orders in the last 30 days
  • orders in the last 60 days
  • orders in the last 90 days

Example formula for 30 days: =SUMIFS(qty, sku, A2, order_date, ">="&TODAY()-30)

Step 4: Join stock on hand

Use XLOOKUP or VLOOKUP to pull stock on hand from the product export into the same sheet, matched by SKU.

Step 5: Add days of cover (optional but helpful)

=IF(sold_30=0,"",on_hand/(sold_30/30))

Leaving it blank when nothing sold avoids a misleading “infinite” value.

Step 6: Sort

Sort by days of cover, lowest first, so the products closest to running out are at the top.

A worked example (made-up numbers)

These numbers are an example only.

Product On hand Sold 30d Sold 60d Sold 90d Days of cover
Ceramic mug 20 60 100 140 10
Wool scarf 45 30 50 60 45
Linen tote 8 12 30 48 20
Gift card holder 12 0 2 5 blank

What this tells you:

  • The mug is selling faster lately (60 in the last 30 days versus 140 over 90) and has only 10 days of cover.
  • The scarf has plenty of stock for now.
  • The tote is slowing down: 12 in the last month versus an average of 16 a month over 90 days.
  • The gift card holder has barely moved, so its cover is blank.

None of this tells you what to do. It gives you the facts so you can decide, based on your supplier lead times, cash and plans. For a step-by-step way to make that call, see how to decide what to reorder on BigCommerce.

Common problems with DIY reports

  • It goes stale fast. The sheet is only as fresh as your last export.
  • Variants and SKUs get messy. Make sure you match on the same identifier in both exports.
  • Big catalogs are slow. Thousands of order lines can make formulas sluggish.
  • Cancelled or refunded orders. Decide whether to include them and stay consistent.

Using an app instead

If you check stock every week, rebuilding the sheet gets old. Runway is a free, read-only BigCommerce app from GrtLabs that shows this report in one table. For each product you see units sold in the last 30, 60 and 90 days, stock on hand, and days of cover. Products that run out soonest are at the top, you can filter to low cover, out of stock or no recent sales, open a product in your BigCommerce admin, and download everything as a CSV. It is listed on the BigCommerce App Marketplace.

Runway only reads orders, products and inventory. It does not create purchase orders, email suppliers or change your stock. If you need purchase orders or supplier workflows, a full inventory system is a better fit. If you need something built around your own process, our team builds custom BigCommerce apps and integrations.

Quick recap

  • Put sales and stock side by side, not just stock.
  • Use 30, 60 and 90-day windows to see the trend.
  • Add days of cover to compare products on one scale.
  • Spreadsheets work; an app saves time if you check often.

FAQ

Does BigCommerce have an inventory report?

You can export orders and products from your BigCommerce admin and combine them in a spreadsheet. Apps such as Runway show units sold and stock on hand together in one table.

How do I see sales by product in BigCommerce?

Export orders with line items, then total quantity per product or SKU in a spreadsheet for the periods you care about, such as 30, 60 and 90 days.

Why compare 30, 60 and 90-day sales?

Comparing periods shows whether a product is speeding up, steady or slowing down, which a single number cannot show.

Can I export my inventory report to CSV?

Yes. A spreadsheet can be saved as CSV, and Runway lets you download its product list as a CSV.

Is Runway free?

Yes. Runway is a free, read-only BigCommerce app from GrtLabs with no upfront or monthly fee.

Coral graphic: days of cover explained, with boxes, an hourglass and the Runway inventory screen
How to Calculate Days of Cover for BigCommerce Products
How to Calculate Days of Cover for BigCommerce Products 1024 538 Nadeem Shaikh

Days of cover tells you how many days your current stock will last if sales keep their recent pace. To work it out, divide the units you have on hand by your average daily sales, usually from the last 30 days. A product with 20 units on hand that sold 60 units in 30 days has 10 days of cover.

That one number makes it much easier to see which products could run out first. In this guide we walk through the formula, a worked example, the tricky edge cases, a spreadsheet method you can use today, and a free app that does the math for you.

What is days of cover?

Days of cover (also called days of inventory cover or days of stock) is a simple estimate: “At the speed this product has been selling, how long will what I have last?”

It is not a forecast and it does not know about next month’s holiday rush. It looks back at recent sales and forward at your current stock. That makes it easy to understand and easy to check, which is exactly why many small store owners like it.

Why it beats looking at stock counts alone

A stock count of 50 sounds healthy. But 50 units of a product that sells 10 a day lasts five days, while 50 units of a product that sells one a week lasts almost a year. Days of cover puts every product on the same scale (days), so you can compare a fast seller and a slow seller side by side.

The days of cover formula

Here it is in plain terms:

Days of cover = stock on hand ÷ average daily sales

And average daily sales is:

Average daily sales = units sold in the period ÷ number of days in the period

Most people use a 30-day period. It is recent enough to reflect what is happening now, but long enough that one busy afternoon does not throw the number off.

A worked example (made-up numbers)

The numbers below are an example only, not real store data.

Say you sell three products:

Product On hand Units sold (last 30 days) Avg daily sales Days of cover
Ceramic mug 20 60 2.0 10
Wool scarf 45 30 1.0 45
Gift card holder 12 0 0 blank

Step by step for the mug:

  1. Units sold in 30 days: 60
  2. Average daily sales: 60 ÷ 30 = 2 per day
  3. Days of cover: 20 ÷ 2 = 10 days

The scarf has more stock relative to its sales, so it has 45 days of cover. The mug is the one to look at first.

The edge case: no recent sales

Look at the gift card holder. It sold nothing in 30 days, so average daily sales is zero, and dividing by zero does not give a real answer. Some tools show “infinite” days of cover, which can be misleading. It makes a product that nobody is buying look like it has endless healthy stock.

A cleaner approach is to leave days of cover blank when there are no recent sales. A blank is honest: “There is not enough recent sales data to estimate this.” It also nudges you to ask a different question about that product, such as whether it needs a price change or a better product page.

Other things to keep in mind

  • New products: If a product launched 10 days ago, a 30-day average understates its pace. Treat the number with care.
  • Stockouts: If a product was out of stock for part of the month, it could not sell during those days, so the average looks lower than real demand.
  • Seasonality: A 30-day window before a big holiday will not reflect the holiday itself. Compare with 60 and 90-day sales to get a feel for the trend.

How to calculate days of cover in a spreadsheet

You can do this without any app:

  1. Export your orders for the last 30 days from your BigCommerce admin.
  2. In a spreadsheet, total the units sold for each product or SKU (a pivot table works well).
  3. Add a column for current stock on hand from your product export.
  4. Add a column for average daily sales: =units_sold/30.
  5. Add a column for days of cover: =IF(units_sold=0,"",on_hand/(units_sold/30)).
  6. Sort by days of cover, lowest first.

This works fine, but you have to repeat it every time you want fresh numbers, and it gets slow with a big catalog.

What is a “good” number of days of cover?

There is no single right answer, because it depends on how long your supplier takes to deliver (lead time) and how much buffer you like to keep (safety stock).

A simple way to think about it:

  • If your supplier usually takes 10 days to deliver, a product with 8 days of cover may run out before new stock arrives.
  • If you want a buffer of about a week on top of that, you might start paying attention once a product drops below roughly 17 days (10 days lead time plus 7 days buffer).

These are example numbers. Your own lead times and comfort level decide the threshold. The data shows you where each product stands; you make the call. When you are ready to turn these numbers into an order, see our simple method for deciding what to reorder on BigCommerce.

A free way to see days of cover for every product

If you would rather not rebuild the spreadsheet every week, Runway is a free, read-only BigCommerce app from GrtLabs that shows this for you. For each product it shows units sold in the last 30, 60 and 90 days, stock on hand, and days of cover, calculated the same way as above (on-hand stock divided by average daily sales from the last 30 days). Products that run out soonest sit at the top, products with no recent sales show a blank instead of an endless number, and you can download the list as a CSV. You can find it on the BigCommerce App Marketplace.

Runway only reads orders, products and inventory. It does not create purchase orders, email suppliers or change your stock. It gives you the numbers; you decide what to order.

If you need something more custom for your store, our team also builds BigCommerce apps and integrations.

Quick recap

  • Days of cover = stock on hand ÷ average daily sales.
  • Use the last 30 days for a recent, steady average.
  • Leave it blank when there were no sales, rather than calling it infinite.
  • Compare against your supplier lead time plus a buffer.
  • Check 60 and 90-day sales to spot trends.

FAQ

What is days of cover in inventory?

Days of cover is an estimate of how many days your current stock will last at your recent sales pace. It is calculated by dividing stock on hand by average daily sales.

How do I calculate days of cover?

Divide units sold in a period (often 30 days) by the number of days to get average daily sales. Then divide stock on hand by that number. For example, 20 on hand ÷ (60 sold ÷ 30 days) = 10 days of cover.

What if a product has no sales in the last 30 days?

Average daily sales is zero, so the formula cannot give a real answer. It is clearer to leave days of cover blank than to show an infinite number.

What is a good days of cover number?

It depends on your supplier lead time and the buffer you want to keep. Many store owners compare days of cover with lead time plus a few extra days of safety stock.

Does BigCommerce show days of cover?

You can calculate it from your order and product exports in a spreadsheet. Runway, a free read-only BigCommerce app from GrtLabs, shows days of cover for each product along with units sold over 30, 60 and 90 days.

Navy GrtLabs graphic comparing a template website with a custom website built around business workflows
Custom Website vs Template Site: Which Fits a Growing Business?
Custom Website vs Template Site: Which Fits a Growing Business? 1024 576 Nadeem Shaikh

A template website is enough when you need a simple, good-looking site fast and your needs match what the template already does: a few pages, a contact form, a blog. A custom website makes sense once your site has to do real work for the business, such as booking, quoting, customer portals, connections to your CRM or ERP, or AI features, or when the template starts fighting every change you want. Many growing companies land in the middle: a solid CMS or store platform with custom pieces built only where they pay off.

The choice is not really about looks. Both can look professional. It is about what the site has to do, who will maintain it, and how much the workarounds are already costing you. Here is how to tell which fits.

What counts as a template site, and what counts as custom?

A template site starts from a pre-built theme on a website builder or a CMS such as WordPress, Shopify or BigCommerce. You swap in your logo, text and photos, and you work within the layouts and features the theme and its plugins already offer.

A custom website is designed and built around your business. The layout, content structure and features are planned for your buyers and your workflows. It can still run on a CMS your team edits every day; “custom” means the parts that matter are built for you, not that everything is hand-coded from scratch.

Custom website vs template: a side-by-side view

  • Speed to launch: templates are faster, because the design and features already exist. Custom work needs discovery, design and build time.
  • Upfront cost: templates cost less to start. A custom build costs more upfront, and the price depends on pages, features and integrations.
  • Fit to your business: a template fits businesses whose needs look like everyone else’s. Custom fits when your process, offer or buyers are different.
  • Integrations: templates rely on whatever plugins or apps exist. Custom builds can connect directly to your CRM, payment gateway, inventory or ERP through their APIs.
  • Performance: many themes load features you never use, and plugin stacking can slow pages down. A custom build can ship only what the site needs.
  • Security and upkeep: every extra plugin is one more thing to update and review. Custom code also needs maintenance, so plan for it either way.
  • Room to grow: templates are easy to start and harder to stretch. Custom is slower to start and easier to extend in the direction you need.

When is a template website enough?

A template is often the right call, and there is no reason to pay for custom work you do not need. It is usually enough when:

  • You are a new or small business that needs a credible web presence quickly.
  • The site is mostly informational: who you are, what you do, how to reach you.
  • Your features are standard: a contact form, a blog, a simple store with a normal checkout.
  • You have a small budget, and the money is better spent on content and marketing for now.
  • You can live with the theme’s layouts without heavy changes.

If that describes you, pick a well-supported theme, keep plugins to a minimum, and put your effort into clear pages and useful content.

Signs you have outgrown your template

Templates rarely fail all at once. They get slower and harder to work with until the workarounds cost more than a proper build. Watch for these signs:

  • Every change is a fight. Small layout or content changes need a developer, custom CSS hacks or another plugin.
  • Your team re-types data. Form submissions, orders or bookings get copied by hand into your CRM, ERP or spreadsheets.
  • The site is slow on phones. Too many plugins and unused theme features weigh down every page.
  • You need a real workflow. Customer logins, a quote builder, booking with payments, dashboards or an admin panel tied to your own data.
  • Plugins conflict or fall behind on updates, and nobody is sure what is safe to change.
  • You look like your competitors. The same theme, the same layout, and nothing that shows why you are different.
  • You want AI features, such as an assistant that answers from your own content, and the template has no clean way to add them.

Where AI fits in the decision

More businesses now want their website to do more than display pages. Common requests include an on-site AI assistant that answers questions from approved content and hands off to a person when it should, natural-language search across product or support documents, and automatic routing of form submissions and orders into back-office systems.

These features depend on two things a basic template rarely gives you: clean, well-structured content, and a site that can connect securely to your data and other systems. A plugin chatbot bolted onto a template can answer simple questions, but if you need answers grounded in your own documents, access controls or hand-offs to your CRM, you are into custom territory. Our guides to retrieval-augmented generation and AI workflow automation explain how those pieces work.

A clear, well-structured site also helps with search, including AI-generated answers: one H1 per page, logical headings, readable URLs and direct answers to the questions buyers ask.

The middle path: a platform plus custom pieces

For many growing businesses, the best answer is not a pure template or a from-scratch build. It is a proven platform with custom work only where it pays off:

  • A content management system your team can edit, with a custom design and page structure built around how your buyers decide.
  • A Shopify, BigCommerce or WooCommerce store with custom features and integrations that off-the-shelf themes do not cover.
  • A marketing site on a CMS, plus a separate custom web app for the portal, booking or dashboard your customers log into.
  • Integrations that move form, order and customer data into the systems you already use, so nobody re-types it.

This keeps everyday editing easy and costs under control, while the parts that make you money work the way your business does.

Questions to ask before you decide

  • What does the site need to do in the next two to three years, not just at launch?
  • Which systems must it connect to: CRM, payments, inventory, ERP, scheduling?
  • Who will update it day to day, and how comfortable are they with the editor?
  • Which manual steps around the website cost your team time every week?
  • Do you plan to add AI features, such as an assistant or smart search?
  • What would it cost you if the site were slow, hacked or down for a day?

If most answers point to standard needs, start with a template. If several point to integrations, workflows or AI, scope a custom or hybrid build before you spend more time on workarounds.

How GrtLabs approaches custom websites

Our custom website development team in Houston builds business websites, web applications and portals, ecommerce stores on Shopify, BigCommerce and WooCommerce, integrations and redesigns. Every build includes mobile-friendly layouts, attention to performance, a security review, a search-friendly structure and an editing setup your team can use without calling a developer for every change. We recommend CMS, store platform or custom code during discovery and explain the trade-offs, then give you a written scope and estimate before work begins.

When the site needs to do more, our AI Factory adds AI assistants grounded in your content and AI automation that routes submissions and orders into your systems, and our digital marketing team brings the right visitors to the new site.

Not sure whether your template still fits? Talk to our Houston team about what your site needs to do, or see how we build custom websites.

Frequently asked questions

When is a template website enough?

A template website is enough when you need a simple site quickly, your content is mostly informational, and your features are standard, such as a contact form, a blog or a simple store. If you can live with the theme’s layouts, a template is often the most sensible choice.

Is a custom website better for SEO than a template?

Not automatically. Search engines care about useful content, fast pages, a clean heading structure and readable URLs. A template can do this well. Custom builds help when a heavy theme or plugin stack slows pages down, or when you need page structures the template cannot support.

Can I start with a template and move to a custom website later?

Yes, and many businesses do. Keep your content well organized and your URLs readable, so a later rebuild can keep the pages that already work and redirect anything that moves.

How much does a custom website cost?

It depends on the number of pages, the features and the integrations involved. A good development partner gives you a written scope and estimate after a short discovery conversation, so you know what to expect before work begins.

Agile practices – they’re not just for software development
Agile practices – they’re not just for software development 1024 614 grtlabs

At Penn Medicine, agile methods have been adopted by a number of information technology teams, including teams that support its enterprise EHR, data analytics, IT operations and systems administration.

Agile software development methodologies such as Scrum and Kanban have been widely adopted by industry software development teams. Although agile practices originated in the realm of software development, other types of information technology teams can benefit from adopting similar approaches.

Fundamentally, agile methods are a set of practices that help teams to collaborate, organize their work, and see it through to completion.

Agile methods for software development

Agile methodology has emerged as a widespread practice for software development in response to the frustrations common in traditional software development projects, with their distinct, lengthy phases of scoping, requirements definition, design, build and testing. Each of these sequential phases can take months, leading to long software development cycles.

Especially in large organizations, traditional software projects can be difficult to manage and unsatisfying for those involved. If you’ve ever had to grapple with business requirement documents that are hundreds of pages long, or if you’ve sat through requirements and design walkthroughs for days on end, only to be disappointed by the software that was eventually delivered nine to12 months down the road, you’ll understand those frustrations.

At the risk of oversimplifying, I would describe agile software development as a shift to short software development cycles (weeks vs. months) and restructuring how people work together to develop software. I have found that these changes significantly improve the experience of software development for all parties involved.

Benefits of incremental delivery

Years ago, before agile methods became widely adopted, I asked one of my software development directors about the release schedule for his products. Since I came from a traditional software development organization, I expected to hear that he had two or three or four major releases per year.

Somewhat apologetically, he replied that his team didn’t have a formal release schedule. They just released features and enhancements whenever they were ready. Although unusual for the time, that incremental, “agile” approach has proven to be an effective way to work for many teams, resulting in improved products and a better experience for team members.

  • Product/usability benefits. Quickly getting new features into the hands of users provides important benefits. Software can only provide value when it is in the hands of end users, so the sooner we release, the sooner we can realize that value. Feedback, whether positive or negative, is best gathered from actual use, so the quicker we get that feedback the better.
  • Benefits to the development team. Short development cycles, for example two weeks, can benefit delivery teams in many ways. Small development tasks are easier to estimate than large ones, which makes meeting delivery deadlines easier. Short cycles establish clearly understood objectives and limit the amount of work in progress. This provides teams with the focus that helps them to drive tasks to completion. Software testing is simplified because a small amount of change is introduced in each release.

Finding better ways to work together

In addition to short development and release cycles, agile methods define a set of practices for how teams work together. A key concept is that the team commits together to getting the work done, which helps reduce overcommitting and finger-pointing.

A common practice is to have small, self-managing, self-organizing teams who interact with each other frequently, for example in short daily “standup” meetings. Another frequent practice is to break work down into units that take a short time to finish (for example, one to three days). In addition, many agile teams work together as a group to estimate work, increasing the accuracy of their estimates.

Beyond software development

Besides software development teams, other teams can benefit from adopting agile methods. Just as the field of project management grew from its early beginnings in engineering and construction into a more generalized discipline, agile methods can be broadly useful for various types of work.

In my organization agile methods have been adopted by a number of information technology teams, including teams that support our enterprise EMR, data analytics, IT operations, and systems administration. Non-IT teams have also followed suit, for example in marketing and our innovation center.

Regardless of the nature of your work, if you are interested in finding a better way to work, consider agile.

Credit: Glenn Fala is the Associate CIO of Application Development at Penn Medicine.