All

Business

A store that takes the payment is not a store that ships the order

Square will charge a card and create an order Printful never sees. What we learned building commerce for Champions League, and the ten minute check every print on demand store should run.

AÉNL Agency••3 min read

A store that takes the payment is not the same as a store that ships the order. Most small brands only find out which one they have when a customer emails asking where their hoodie is.

That gap is the most useful thing we have learned building commerce for Champions League, a music and apparel brand we have worked with for six years. The work spans the storefront, the newsletter, the music and the merch. This is a look at how it is put together, and at the one integration pattern we now check on every store we touch.

What the store actually is

Champions sells merch, CDs and vinyl from one storefront, and nothing sits in inventory. Apparel is print on demand through Printful, so a sale triggers production instead of pulling from a shelf. That changes the economics of a drop: there is no minimum order, no unsold boxes, and a new design costs a mockup, not a print run.

The store also carries a music player that keeps playing across pages and survives a reload, because for a music brand the catalogue is the reason people are on the site. A shopper can browse sweatshirts while the record keeps going. Small product decisions compound here: we split combined "size, style" variations into two separate selectors, preselect the variation a shopper chose when they open an item, and link each bag thumbnail back to its product page. None of those are features anyone asks for. All of them remove a reason to abandon a cart.

Around the store sits the rest of the system: a newsletter landing page that captures fans between releases, and campaign work that sends people to it. The store is one surface of a brand, not a standalone project.

The failure that looks like success

Here is the pattern worth checking on your own store. Square's Payments API will happily charge a card when you send it nothing but an amount. Square then creates an order behind the scenes so the payment has somewhere to live. The trouble is what that order contains: a single custom amount line, with no catalog item attached and no shipping fulfillment.

Printful's Square integration only acts on orders that carry catalog line items and a shipping request. A custom amount order looks, to Printful, like an in-person sale at a counter. So the customer is charged, the dashboard shows revenue, and the production queue stays empty. Nothing errors. Nothing alerts.

Two habits make it worse. The first is writing order details to your own database and logging failures with a bare console.error: if the insert is rejected, the record simply never exists and no one is told. The second is letting the browser send the amount to charge. If the client sets the price, the client can change the price.

The fix is not exotic. Build a real Square order from catalog items, with a shipment fulfillment and the customer's address, compute the total on the server from those items, and charge against that order. Then make every write that can fail say so loudly, somewhere a person will see it.

Why this is a maintenance problem, not a build problem

The uncomfortable lesson is that integrations rot quietly. A store can launch correctly and drift: an API version changes, a product gets recreated with a new ID, a token expires. Each of those produces the same symptom as the pattern above, which is money in and nothing out.

That is why we now treat a storefront as something to monitor, not something to deliver. The checks are cheap: a nightly test order through the full path, a comparison between payments taken and fulfillment requests created, and an alert the first time those two numbers disagree. If you run a print on demand store, run that comparison for last month today. It takes ten minutes and it tells you whether you have a store or a payment form.

If you would rather someone else watch it, that is exactly what our retainer plans are for.

Bluehost
Square Point of Sale

Make your work stand out with systems built by indie engineers and operators.