How to Write a Custom Hat Brief Your Manufacturer Can Use
Most custom hat briefs miss the detail that decides the first sample: colour. What a hat maker actually needs, from Pantone codes to vector logo files.
Most custom hat briefs arrive the same way: a logo, a colour named loosely, a quantity, and a date. Sometimes a mood board. Occasionally a reference hat. These briefs are not wrong, but they are usually missing the one or two details that decide whether the first sample comes back looking like what the client pictured. This is a short guide to what a hat maker actually needs, and why each item matters.
Colour: be specific
"Navy" is not a colour specification. It is a family of shades, and the navy on screen is not the navy that will appear on fabric. The same applies to forest green, off-white, and most other named colours. A screen shows colour with light. Fabric shows colour with dye. The two do not translate directly, and the gap between them is where most first-sample surprises come from.
A Pantone code is the useful reference, because it describes a colour in a way a dye house can match. If you do not have one, a physical swatch or an existing product in the right colour works almost as well. A screenshot of a hex value helps the conversation but does not translate directly to dye, so treat it as a starting point rather than a specification.
If exact colour matching matters to your order, say so in the brief. It affects the sample process, the time the order takes, and sometimes the material options available, because some colours are easier to hit on some fabrics than others. Flagging it early is always cheaper than discovering it on a finished run.
Logo: the file format matters
An embroidered logo starts as a digital file and ends as stitching instructions. A vector file (AI, EPS, or SVG) gives the embroidery team the cleanest input, because it can be scaled and converted to stitches without losing definition. A high-resolution PNG is workable. A JPEG pulled from a website is usually not, because it rarely has the resolution or clean edges the conversion needs.
Some designs are harder to embroider than others. Very fine lines, small text, and complex gradients do not always survive being rendered in thread, where the smallest reliable detail is set by stitch size rather than pixel size. None of this means a logo cannot be used. It means flagging it upfront lets the team adjust the artwork once, at the start, instead of discovering the problem on a sample. If the logo has specific brand colours, supply those as Pantone references too, so the thread can be matched the same way the fabric is.
Quantity: order what will be used
The right quantity is the one people will actually use, not the one that brings the unit price down. Over-ordering is one of the most preventable sources of waste in branded merchandise. Every unit in a run that is never worn carries its full production footprint, and the per-unit saving on a larger order rarely offsets the cost of storing or discarding the surplus. A smaller order of hats that all get worn is almost always a better outcome than a larger order where a third sit in a box.
Timeline: which program fits
Quantity and date together decide which production route makes sense. As a rough guide, a fully custom hat needs the most lead time, a part-customised hat on a pre-made base needs less, and a blank or lightly branded hat can move fastest. Telling the maker your deadline at the briefing stage lets them steer you to the route that can actually meet it, rather than promising a timeline the custom process cannot support.
Note to verify before publishing: confirm the current program names and lead times (for example Classic, Expedited, and Blank) with the team before stating them.
After the brief is submitted
Requesting the custom order guide at topiku.co/custom-hats is the first step. The team follows up by email, usually within one to two business days. The first conversation covers what the order needs, what timeline is realistic, and anything worth clarifying before a sample is started.
A digital mock-up is produced for approval before any physical sample begins. Once the digital version is confirmed, a physical sample follows for orders where colour accuracy or construction detail is critical. Full production starts only after sign-off. Each stage exists to catch a problem while it is still cheap to fix.
Note to verify before publishing: confirm the current response time with the team before stating it as one to two business days.
Why we do not skip the sample
The request comes up regularly: can we skip the sample to save time? The logic makes sense until a run of two hundred hats arrives in a colour that did not translate the way the client expected. The sample exists to catch that when it costs one hat to fix, not two hundred. The better way to protect a tight timeline is not to remove the sample stage but to plan the brief well enough that the sample passes on the first try, which is what a Pantone code and a clean logo file make possible.
The short version
A good brief is four things: a Pantone code, a vector logo file, a quantity that matches real need, and a date. With those, the team can take the order from mock-up to finished hats with the fewest surprises. Start at topiku.co/custom-hats and the team follows up from there.
Works Cited
1. Topiku. Custom Hats. https://www.topiku.co/custom-hats
