Three Cubes: The wallmarkets Brand

The wallmarkets logo is three interlocking cubes. People keep asking what they are supposed to mean. The honest answer is that the design started with constraints, not symbolism. The meaning came from solving the right practical problems.

The problem the mark had to solve

From the start, we wanted a mark that pointed at what the product actually does: coordinate multiple moving parts, keep operations structured, and make a complex system feel legible.

That is the job of the product itself, of course, but the identity still matters. A wordmark on its own was usable and completely forgettable. We needed a symbol that could survive at tiny sizes - favicons, printed delivery notes, mobile home screen icons - and still feel like it belonged to the same product.

The logo had to work in places most identity systems conveniently ignore. A dashboard header is forgiving. A small browser tab is not. A thermal printout is not. A low-end phone screen in daylight definitely is not.

Why cubes

Cubes are boxes. They are the physical units moving through the system. Using three of them, locked together, immediately suggested that the objects were not isolated. They were part of a coordinated whole.

That mattered because logistics is not a collection of separate tasks. A missed delivery, an unprocessed return, or a stock count that is slightly off does not stay isolated for long. One small failure tends to ripple outward. The interlocking shape captured that better than anything more decorative did.

The other reason cubes won is simpler: they remain readable when reduced aggressively. Many of the more "expressive" directions we tried looked interesting on a large artboard and collapsed completely when shrunk to practical sizes.

The practical decisions

The mark had to work at 16x16 pixels. That sounds trivial until you test it. At that size, anything overly detailed turns into a blob. Three simple forms held together much better than more ambitious ideas, and that one requirement eliminated a surprising number of candidates very early.

The color choice was just as practical. We wanted something that felt reliable and technical without defaulting to the generic logistics-software blue that everyone else seems to reach for. The blue-violet range gave us that balance, but only after we checked it in light mode, dark mode, print, and small-size use.

Dark mode mattered from the beginning too. We did not want a mark that only worked well on light surfaces and needed awkward inversion elsewhere. The geometry had to stay intact in both contexts.

What we rejected

We rejected a lot of perfectly respectable logo ideas for very boring reasons.

Some marks looked too much like warehouse clip art. Some felt like generic SaaS abstractions that could have belonged to literally any software company. Some depended too heavily on gradient nuance and stopped working the second they were printed in black and white.

A few directions looked impressive in presentation slides and terrible as favicons. That is a useful failure mode to notice early.

The identity needed to survive contact with real operational use, not just with branding decks.

Why print changed the design conversation

One thing people underestimate about logistics software is how often the brand appears in print. Delivery notes, credit notes, and warehouse paperwork still matter. In some environments they matter more than a polished website.

That changes how you think about identity.

If the mark breaks down on a thermal printer, if the contrast disappears on a photocopy, or if the shape muddies at receipt size, you do not really have an operational brand. You have a screen-only brand.

We wanted something that still looked deliberate when it appeared on paper in the least flattering possible context.

What consistent brand identity does operationally

A logo does not sell software by itself. The product has to do that. But a consistent identity still matters because it signals care and creates recognition.

For a platform people use every day, recognition is not abstract. When the wallmarkets mark appears on a printed delivery note, the supermarket receiving team knows where it came from. When it appears in the dashboard a driver opens every morning, it reinforces the sense that they are in the same system from one touchpoint to the next.

That kind of consistency is easy to dismiss because it is hard to measure. But in operational software, small things compound. The three cubes are one of those small things.

Why this still matters to an engineering-first company

We do not think design sits in opposition to engineering seriousness. Quite the opposite. Good identity work, like good product engineering, is about reducing ambiguity and surviving real constraints.

The logo became useful for the same reason good software becomes useful: it was forced to work under the conditions where the product actually lives.

That is why the mark ended up the way it did. Not because three cubes sounded poetic in a workshop. Because they kept working after everything less disciplined had failed.