This week's website work was mostly about making the custom builder feel less like it was hiding things in weird cupboards. The patchpanel.ca experience should be a little clearer, a little harder to break, and a little less likely to make you wonder whether the computer has developed opinions about your patch. It has not. Probably.
More choices, fewer missing buttons
Several builder options now show up more reliably where customers expect them. The Glow Border option is available on the 3 x 2 and 3.5 x 2 ID Panel sizes when those sizes support it, instead of only behaving nicely on the larger 4 x 2 size. That is the kind of small checkbox problem that feels tiny until you are the person trying to order the exact thing.
Name Tape and Cover Panel sizing also expanded. The builder now recognizes the new 8 x 1 Name Tape size, plus the larger 10 x 4 size for Name Tapes and Cover Panels. These are regular selectable sizes, not secret menu items, because secret menus are for restaurants and developer regret.
For Custom Printed Patches, white is now easier to choose as a bleed colour when it appears in image-based swatches. That matters when the cleanest edge for your design is plain white, which is apparently a thing computers needed a stern talking-to about.
Previews that tell fewer little lies
Symbol Patch previews were cleaned up to use proper vector sources for the small, large, and 3.5 inch hex options. That means the builder preview, the modal measurements, and the final cut path are better aligned with the actual symbol data, rather than leaning on older fallback images.
Printed patch previews also got a reliability pass. Restored designs now scale their saved image placement more carefully, so artwork is less likely to come back clipped after a reload, edit session, or different screen size. Contour and bleed handling received similar attention, especially for cases where the preview looked fine but the exported artwork could get a little too creative. We prefer the patch to be creative, not the bug.
Add to cart got stricter in the useful way
The Custom Printed Patch builder now uploads the final preview assets when you add the item to cart, rather than repeatedly uploading every settled edit along the way. The tradeoff is a slightly more obvious preparing step at the end, but the benefit is cleaner cart data and fewer unnecessary uploads caused by every drag, rotate, or colour tweak.
We also tightened how printed patch line items are identified, so two patches using the same image but different sizes or settings do not collapse into one another after checkout. Identical items can still behave like identical items; different items stay different. Revolutionary stuff, if your revolution is mostly about not losing a patch.
Jacket Panel add-to-cart behavior is stricter too: if the builder cannot produce the required production-ready data for a jacket-style patch, it blocks the submit instead of letting a bad order sneak through. Less mysterious follow-up later, more useful signal now.
Better recovery when browsers or edits get weird
The site now handles Instagram and Facebook in-app browsers more gracefully, especially on Android, where injected browser scripts could break page loading. Those in-app browsers remain tiny chaos boxes, but at least patchpanel.ca has a better helmet.
Post-order custom patch edit sessions now show clearer unavailable-session messages instead of dumping customers into a blank mystery error. Repeated saves in an edit session were also hardened so customers can make another change without having to reload and hope the internet spirits are feeling generous.
Cleaner after-order communication
Customer update emails now do a better job showing what changed, including original and new previews when available, and they sign off as the PatchPanel Team. Shipping tracking links for Stallion shipments were also corrected so the link in the shipping email points to the right tracking page. Small detail, large reduction in sighing.
That is the week: more visible options, sturdier previews, cleaner cart handoff, and fewer places where the website can act like it just learned what a patch is. Build something weird. The builder is getting better at keeping up.
