The artist is named on every product, because the database will not let us forget.
Support Brutal Music sells dark art apparel by independent artists, and pays them on every sale. Empyria built it on WordPress and WooCommerce with the artist modeled as a taxonomy rather than a credit line, so attribution is structural. Every product carries its artist, and every artist has a page of their own.
A promise nobody can check
Every merch store says it supports artists. The print-on-demand marketplaces say it loudest, and they are also the ones that strip the artist's name off the product page, pay a few percent, and make the design searchable by nothing but the garment it is printed on. A buyer who wants to support an artist has no way to tell the difference between a store that does and a store that says it does.
That is the actual problem this business is solving, and it is not a marketing problem. It is a data problem. If the artist's name is typed into the product description, it is a habit, and habits fail at product two hundred. If the artist is a record that products belong to, attribution cannot be forgotten, and it can be browsed, counted, linked to, and paid from.
There is a second thing, less obvious. On a storefront, the content that decides a sale is almost never the product copy. It is shipping times, return policy, sizing, and what happens if the print is wrong. Most stores bury all of it in one terms page of four thousand words, which is the same as not having it.
Five decisions, made once
Each one is something a purchased storefront theme does the other way round.
The artist is a taxonomy, not a credit line.
Every product is assigned to an artist the way it is assigned to a category. That produces an artist archive with a page per artist automatically, makes "everything by this person" a real link rather than a search, and means the attribution promise is enforced by the system rather than by remembering. It also means the day there is a royalty report to produce, the data is already shaped for it.
People shop by mood, so there are two ways in
Product category answers "what is it," which is the question you ask second. A separate theme taxonomy answers "what is it about," which is the question you ask first: horror, occult, cosmic horror, heavy music. One catalog, two doors. Storefront themes ship with one, and it is always the wrong one.
The help center is a content type, not a page.
Seven topics covering ordering, shipping, returns, payment, sizing and care, artists and licensing, and account privacy. Each answer is its own document with its own URL, which means it can be linked from checkout at the exact moment the question occurs, and it can be found by someone searching the question in a search engine rather than on the site.
Legal is a content type too.
Six documents, separately maintained: privacy, terms, shipping, returns, accessibility, and a copyright and DMCA policy. On a store that prints other people's artwork, the DMCA policy is not boilerplate, it is operational, and burying it in a footer link to a wall of text is how a real takedown request becomes a bad afternoon.
No purchased storefront theme.
WooCommerce for the commerce, Bricks and a custom child theme for everything the customer sees, with the whole design system in one stylesheet. The store does not rent its own appearance from a vendor who can change the price, drop the product, or ship an update that rearranges the checkout.
Anyone can put "we pay our artists" in a footer. Only a database makes it impossible to stop.
The decision the whole build hangs on
The build
Fourteen pages on WordPress, Bricks and WooCommerce, on a custom child theme holding the entire design system in one stylesheet. No purchased theme, and no license that has to keep being renewed for the store to keep working.
- A custom artist taxonomy, so every product carries its artist and every artist gets an archive page without anyone creating one.
- A second theme taxonomy, so the catalog can be browsed by what a design is about rather than what it is printed on.
- A help center as its own post type with seven topics, each answer separately addressable and linkable from the point of sale.
- Six legal documents as their own post type, including a copyright and DMCA policy written to be used rather than to be quoted.
- An artist program page and a careers page, because a store that wants submissions has to explain the deal in public.
- A giving program that sees a total of 10% of net revenue from every sale donated to a charity
What happened, without a percentage
Same as CPC: I own this company, so a statistic I generate about it is marketing with a decimal point in it. What I can tell you is what the structure does.
Attribution survives scale. At four products you can remember to credit the artist. At four hundred you cannot, and every store that relies on remembering eventually ships a product with no name on it. This one cannot, because there is nowhere to put a product that does not belong to an artist.
The questions that block a sale have their own addresses. Sizing, shipping and returns are seven documents rather than one policy page, which means the answer can be linked at the moment of doubt rather than hunted for.
Adding a design is not a project. New product, assign an artist, assign a theme, and the artist page, the theme browse and the artist's back catalog all update themselves. That is the difference between a store that grows and a store that gets abandoned at ninety products.
And the thing it is really proving. CPC shows I understand a sector. This one shows I can model one. A client whose business has a rule in it, which is most of them, is buying the second thing.
Your field has its own version of this.
Every sector has three or four things its websites get wrong that cost real money. Finding them is the first half of the job. Tell me what you are building and you will hear back within one business day.