We Build Our Own Tools. Now We're Sharing Them.

When a piece of software doesn’t fit the way we work, we don’t change how we work. We change the software.

That has been the quiet habit at Initiative Distribution for a while now. Somebody on the floor hits the same annoying wall three days in a row, mentions it, and instead of shrugging and living with it, we build the small thing that makes it go away. A label that prints the way we actually need it. An alert that tells us a store connection went quiet before the missed orders pile up. A form that fills itself in so nobody is retyping the same freight details at 4 p.m.

None of that was ever meant to be a product. It was just us fixing our own problems. But we kept noticing that other operations teams have the exact same problems, and most of them are stuck waiting on a software vendor to care. So we’re doing something we probably should have done sooner: sharing the tools.

We’re calling that effort Initiative Edge, and this is the announcement that it exists.

Why we write our own software at all

We’re a 3PL. We ship other people’s products. On paper, we have no business writing code.

But we’ve been at this for 20-plus years, and one thing you learn running a warehouse that ships to 120-plus countries is that off-the-shelf software is built for the average operation, and nobody actually runs the average operation. Every client we take on has something a little strange about them: an odd kit, a fragile item, a receiving quirk, an assembly step that has to happen in a specific order. Big systems handle the strange stuff by making you pay for a change order and wait a quarter.

We’d rather just build the thing.

The reason we can is that we know the work. We’re not a software company guessing at what a warehouse needs. We’re the people on the floor who felt the problem, which means the tool that comes out the other end tends to be small, specific, and genuinely useful instead of a pile of features nobody asked for. When you already understand the edge cases and the cost of getting an order wrong, building the fix is fast.

The first three tools

Here’s what’s available right now. Each of these started as something we built for ourselves and then cleaned up enough to hand to somebody else.

ShipWatch watches your ShipStation store connections and tells you the moment one stops responding, before missed imports turn into a backlog and an angry customer. We built it because finding out about a dead connection after the fact is a bad afternoon, and we didn’t want any more of those.

Label Maker turns a SKU, a title, and an image into a clean, printable label with a barcode that actually scans. It handles the common barcode formats and standard label sizes, single labels or a full sheet. It’s free. We use it every day.

FreightBill generates a bill of lading. You fill in the shipper, carrier, consignee, and freight lines, and it gives you a clean one-page BOL with the totals added up for you, ready to print or save as a PDF. No signup, no account, nothing stored on a server. Also free, because it should be.

That’s the whole pitch for each of them: a small, sharp tool that does one job well. If you run any kind of fulfillment or operations, at least one of these probably scratches an itch you’ve been living with.

Big client or small, it’s the same shop

The thing we like most about working this way is that it makes the size of a job almost irrelevant.

A large client with a complicated setup gets a tool built around their setup. A brand shipping a few hundred orders a month gets the same attention, because the tool is cheap for us to build and adjust. We’re not spinning up a six-month software project either way. We’re making the specific thing the work needs, and we can turn it around fast because there’s no committee, no roadmap meeting, and no vendor in the middle.

That’s what being small and independent actually buys you. Not lower prices as the headline, but the ability to move. A client mentions a problem on a Tuesday and there’s a decent chance we’re testing a fix by Thursday. Try getting that out of an enterprise WMS.

Where this goes

Initiative Edge is going to keep growing the same way it started: a real problem shows up in the warehouse, we build a tool for it, and if it turns out to be useful beyond our four walls, we release it. We’re not going to list a bunch of things that don’t exist yet or promise a grand unified system. When there’s a new tool worth using, it’ll show up on the Edge page and we’ll say so.

For now, go poke at the three that are live. Break them. Tell us what’s missing. That feedback loop is exactly how they got good in the first place.

And if the way we work sounds like the kind of fulfillment partner you’ve been looking for, that’s not a coincidence. The same instinct that makes us build our own tools is the one that makes us pay attention to the details of your operation. That’s the whole company, really.