Logbook For Custom Keycaps Weekly

Tracking Your Keycap Builds Without Losing Your Mind

I spent three years managing custom keycap orders across multiple vendors, and let me tell you the hard way that Excel alone won't cut it. Logbook For Custom Keycaps Weekly is one of those tools that sounds obvious once you've been bitten by the "I totally forgot what I ordered and when it shipped" problem at 2 AM before a product launch. It's not a spreadsheet template. You've probably seen those Google Sheets floating around with rows for profile, material, kit size, and a checkbox column. I made those too. They work until you have eight simultaneous orders across Wycliffe, GMK, and three different artisan suppliers, then suddenly you're checking three different sheets to figure out which keycaps are actually arriving next Tuesday. The weekly logbook format was designed by a group of keyboard modders who realized the standard monthly overview missed the granularity you need when things ship on weird timelines. Mechanical keycap order tracking involves more moving parts than most people expect. There's the production wait, the shipping window, the customs hold risk for international orders, and then your actual build schedule.

How It Actually Works in Practice

The system breaks each week into a simple but structured format. You log an order entry when you place it, then update it through the lifecycle: confirmed, in production, shipped, received, mounted. That's it. The power comes from the filtering. Here's where beginners mess up. They try to log everything including keycaps they're only thinking about buying. Don't do that. Only log orders you've actually paid for. I learned this the hard way when my "potential purchases" column took up 60% of my log and I couldn't find the one order I actually needed for an upcoming event. The logbook stays clean when you treat it like a tracking tool, not a wishlist. The weekly view gives you a snapshot. Every Sunday night, you look at what's scheduled to arrive the following week, what's stuck in production, and what you need to prep for mounting. This usually takes me about twelve minutes. Before I switched to this system, I was spending hours digging through email confirmations and PayPal transaction history trying to figure out what was actually coming.

The Real Workflow

You need three pieces of information for every entry, and nothing more: order reference number, vendor, and expected delivery date. Everything else is optional. I've seen people add columns for switch type compatibility and keycap art descriptions, and while that sounds organized, it becomes a maintenance burden you'll abandon within a month. Update frequency matters more than you'd think. Log the order immediately after payment. Then check your vendor's production updates weekly, not daily. Keycap manufacturers don't give real-time status, so checking every day just creates anxiety without new information. Mark it shipped when you get the tracking number, and mark it received when the package hits your desk. The mounting phase is where most people skip documentation. Log which profile you're using, what the switch interaction feels like, and any quirks. I use a simple notation: Cherry for MX-style switches, BOB for bullet profile, and then notes about actuation feel. This saves you from remounting the same board three times because you forgot why you switched layouts the first time around.

Edge Case That Almost Drove Me Crazy

Here's a specific problem that took me weeks to solve. I had a batch of artisan keycaps ordered from three different makers on AliExpress, all with different production times and shipping methods. Two arrived in time, one got stuck in customs for eleven days, and I had a full board waiting for nothing. The logbook had the tracking numbers, but there was no easy way to see which package was which when they all had similar transit times. My workaround was simple but I wish I'd done it sooner. I added a second column called "tracking prefix." Different carriers use different prefix codes, and I just noted them down. USPS starts with 94, FedEx uses 17 or 79, DHL uses 00. When a package shows up at my door with no label details, I can look at the tracking prefix in my log and immediately know which vendor it came from. This cut my confusion time from about twenty minutes per shipment to roughly thirty seconds.

What This System Doesn't Fix

Let me be clear about the limitations. A logbook won't speed up your vendor's production. It won't help with keycap shortages, which seem to hit the market every six months now. And it definitely won't prevent you from impulse ordering a second set of PBT doubleshot keycaps you already have three of. If you only have one or two ongoing orders at a time, this is overkill. A simple notes app or even a physical notebook works fine. The system really shines when you're juggling four or more concurrent orders, which is when the complexity of remembering which kit is which actually becomes painful. There's also the data portability issue. If your logbook is stuck in a proprietary format or a Google Sheet you no longer have access to, you've lost everything. I export my entries to CSV monthly and store them locally. Five minutes of work that saves you from total data loss.

Alternative Approaches Worth Considering

Some people prefer Notion databases for this. They offer better filtering and linking between orders and builds. The tradeoff is you're dependent on Notion existing and your internet connection working. For me, the simplicity of a flat CSV file beats the fancy features every time. Others use dedicated inventory software meant for retail businesses. That's like using a freight train to carry groceries. You'll spend more time configuring the system than actually tracking keycaps. The weekly logbook format works because it matches how mechanical keyboard hobbyists actually think about their orders. We plan builds in weekly chunks, not monthly, because production delays and shipping windows don't respect our quarterly goals. The granularity matters more than the tool's features.

If you want to start, begin with a simple spreadsheet. Create columns for order date, vendor, order reference, expected delivery, actual delivery, and mounting notes. Update it once a week on Sunday. You'll have a working system in an hour and a reliable record within a month. I've been running this system for about two years now. My current log has forty-seven entries, and I can pull up any order from the past eight months in under ten seconds. That's the actual value proposition: not the complexity of the tool, but the time you save digging through email threads and PayPal receipts when you need specific information quickly.