What we have built for online stores

Case notes

• Sell delivery speed, not carrier names, at checkout

  Shoppers pick "2 Business Days" instead of a carrier. The store charges the cheapest real service for that speed, and ShipStation is told which service to buy the label for. If the price paid and the label price cannot be matched, a person reviews the order instead of the app guessing.

• What a card processor asks for before approving a regulated store

  We built all nine items on a processor’s checklist into a custom store: an age gate, card logos, policy pages, a contact page, account-only checkout, and required checkout fields. Proof of each customer’s consent is saved on the order. The application is in review.

• Show certain products only to logged-in or returning customers

  A BigCommerce theme filter that hides chosen product lines from guests everywhere a product can appear: category pages, search, carousels and menus. A stricter mode shows them only to customers with a past order. Built, tested and deployed.

• Turn off card brands at checkout

  An on/off switch per card brand. The checkout hides the logos of brands the store cannot accept and shows a clear message if a shopper types one in, before they submit payment.

• One rule list for checkout, marketing and public pages

  A read-only feed of the store’s live shipping rules, so marketing tools and public "where can we ship" pages always match what checkout enforces.

• Saturday delivery upgrade

  A paid Saturday delivery checkbox at checkout that only appears late in the week, and only on rates that can deliver on Saturday.

• Free priority shipping by loyalty tier

  Checkout looks up the shopper’s loyalty tier and makes one delivery speed free above a spend level that drops as the tier rises. If the loyalty system is slow or down, checkout works as normal.

• Several stores on one shipping setup

  Each store keeps its own shipping rules, and a full setup can be exported from one store and imported into another. When a carrier account is replaced, its rate settings move in one action.

Case notes

• Give your ad agency a live list of what to promote, and where not to

  The outside ad agency logs in and sees which products are on promotion right now, with the states where each one must not be advertised. A spreadsheet export includes the same columns.

• Campaign placements in the theme

  Empty placeholders on product cards, product pages and the cart that the promotions tool fills in, so marketing staff run campaigns without theme changes. A site-wide banner for a sweepstakes went live the same day it was requested.

Case notes

• An owned alternative to Yotpo Reviews on BigCommerce

  Product reviews, star ratings, photo and video reviews and search engine review markup from one script. This retailer was paying about $6,000 a year for its reviews plan and was quoted $13,000 a year to lift a cap on review request emails. The owned version has no send cap.

• Switch from Yotpo without losing reviews or points

  More than 33,000 reviews moved over with their photos and videos, and loyalty members kept their balances and tiers. Both imports start with a preview and are safe to run twice.

• Review request emails with five clickable stars

  A branded request goes out after each order. Clicking a star opens a short page already set to that rating. Staff can also send one-off campaigns to past buyers of a brand or product.

• Newsletter and cart events for a custom store

  Sign-up forms and cart, checkout and order events sent to Omnisend from a custom-built store that the email platform does not connect to on its own.

Case notes

• See what your shipping restrictions cost you

  A dashboard that shows how many orders the rules stopped, what they were worth, and where they came from, by state and by product. It separates orders stopped at checkout from orders cancelled afterward, and counts a shopper who retries several times as one lost sale.

• Profit by channel across Odoo, BigCommerce and ad data

  One reporting area for the owners that joins ERP orders, storefront data, ad platform data, web analytics and shipping costs, with a weekly email digest.

• Scheduled revenue sync from BigCommerce

  Each store’s completed order revenue is pulled every five minutes and stored as daily totals, so reports load from the database and stay inside BigCommerce’s rate limits.

Case notes

• A request desk for marketing and IT asks

  Staff file requests in one place and each becomes a tracked ticket. Replies by email are added to the ticket, and a ticket reopens when someone replies after it is done.

• A central hub for a multi-store BigCommerce retailer

  What began as a small tool for sale badges grew into the place where the marketing team plans promotions, the owners read reports, the ad agency checks what to advertise, and the support chatbot gets its answers.

• Fill in missing product specs across a large catalog

  Specs buried in product descriptions are pulled out in bulk, first by rules and then by a language model for what the rules cannot read, with a dry run before anything is saved. Specs were saved for more than 6,700 products.

• Match products between two storefronts

  Sister stores numbered the same products differently. Matching ran in steps: ERP listings, then title, then SKU, then a suggested match for the rest, with a review screen for staff. Every one of more than 3,800 products got a decision.

• Large catalog sync without timeouts

  A sync that reads one page of products at a time and queues one small job per product, so catalogs of thousands of products finish instead of stopping partway.

• Theme playbooks for sister stores

  One-off theme changes were written up as step-by-step playbooks so they can be repeated on a sister store, and the theme repository was cleaned up so every change goes through review.

Case notes

• A faster, custom storefront for Odoo

  A custom-built store that runs apart from Odoo but uses Odoo for products, prices, stock and orders. Catalog pages are served from a cache and refreshed every 60 seconds, while carts and checkout always talk to Odoo live.

• One Odoo database, several brands, separate websites

  One storefront shows only its own company’s products, even though the database holds several businesses. If no company is set, the store shows nothing instead of everything.

• Show price per unit and sort by it on BigCommerce

  A unit price on product cards, product pages and bulk price tiers, with sorting and range filters BigCommerce does not offer. In testing, 843 product cards were checked against an independently worked out value and all matched.

• The error that said "Added successfully"

  Guests on a custom Odoo store could not add to cart, and page views were creating empty orders. Both had one cause, hidden behind a success message. Keeping guest carts in the storefront fixed both without changing Odoo.

• Let the marketing team edit the site

  A content editor for the homepage, product page details and search engine text on a custom store, while products, prices and stock stay in the ERP.

• Brand landing pages and a state-by-state shipping map

  Custom landing pages for each brand a store carries, with descriptions and FAQs, plus a clickable US map page that shows where products can ship.