Freelancers using SAPFreelancers using SAP
I fix warehouse chaos SOPs, SAP & Excel system for ops team
5.0
Rating
7
Followers
I fix warehouse chaos SOPs, SAP & Excel system for ops team
Cover image for Most warehouse audits I've seen
Most warehouse audits I've seen focus on the wrong things first. Neat labels, clean floors, a binder full of SOPs nobody's opened in months — all of it can look great and still sit on top of a warehouse that's quietly bleeding money. And the SOP binder is usually worse than just outdated. Somewhere along the way, the actual process changed — someone found a faster way to do something, or worked around a problem — and that change lived in their head, not in the document. Everyone just adapts and moves on. Then that person leaves, and suddenly nobody can explain why the process works the way it does, because the only place it was ever really "written down" walked out the door. If I only had fifteen minutes to walk a warehouse, here's honestly what I'd check. I'd skip the month-end accuracy report and ask what's mismatched right now, today. A clean number at month-end really just tells you how good someone is at patching things up before a deadline. Asking about today tells you whether the process actually holds up when nobody's paying special attention to it. Then I'd go find one picker and just watch them complete one real order, start to finish — not a demo, an actual order in the middle of a shift. You learn more in five minutes of watching someone walk a pick path than you do in an hour of reading reports. How far they're walking, how often they double back, how many times they have to stop and ask someone where something actually is. I'd also want to know how long stock sits between receiving and put-away. Not how fast it gets scanned in — how long it physically sits on the dock before it's properly stored. That gap, more than almost anything else, is where damage, shrinkage, and "we can't find it" problems quietly start. And I'd ask a warehouse worker why something's done a certain way — not a supervisor. If the answer is "that's just how we've always done it," that's usually a process nobody's questioned in years, or worse, a workaround that only exists in that one person's head. Last thing, I'd look at what's actually sitting near the exit versus what's actually fast-moving. Layouts get set once and almost never revisited. More often than you'd think, the stuff people grab constantly is buried in the back, and something nobody's touched in months is sitting right up front for reasons nobody remembers anymore. None of this needs a clipboard or a formal audit template. It just needs fifteen minutes and being willing to ask "why" one more time than feels comfortable — because the answer might only exist in one person's head, and that's the real audit finding.
0
9
Cover image for Why your SAP data is
Why your SAP data is inaccurate — and it's not SAP's fault. Every time someone tells me "our SAP data is a mess," I ask a few questions, and almost every single time, the answer has nothing to do with SAP. The system did exactly what it was told, exactly when it was told. If the number on screen doesn't match what's actually on the shelf, something happened on the floor that never made it into the system — or it made it in late, or someone found a shortcut because doing it properly during a busy shift felt like a luxury nobody had time for. Picture this: the shelf says 40. SAP says 42. Nobody's lying — the count on screen is just repeating something that was entered wrong, or late, or never corrected. I've seen the same handful of patterns show up again and again, at different sites, with completely different teams. Someone unloads a truck, and the goods receipt doesn't get posted until hours later because paperwork felt like it could wait until things calmed down. By the time it's finally entered, nobody actually remembers if it was 40 units or 42 — so whatever gets typed in is really just a best guess dressed up as data. Or transactions get batched at the end of a shift instead of logged as they happen. The timestamps look fine, but the actual sequence of events is gone, which means when something doesn't match later, there's no way to trace back what caused it. Or someone just overrides the number to make it "correct" for now, without asking why it was wrong in the first place. That fixes the symptom for exactly one day. The actual cause is still sitting there, waiting to cause the same problem next week. And honestly, a lot of training doesn't help either — people get taught which buttons to press, but nobody explains why the timing or the order of steps actually matters. So they follow the steps, but they have no idea what breaks the moment one gets skipped. None of this ever shows up as a system error. It just shows up as "SAP's wrong again," which is usually the one explanation that isn't actually true. The fix is almost never a system change. It's a behavior change — closing the gap between the moment something physically happens and the moment it gets recorded, and making the right way to log it the easy way instead of the slow one. If your numbers keep drifting from reality, the system isn't lying to you. It's just repeating exactly what it was told.
0
23
Cover image for I spent the first couple
I spent the first couple of years treating inventory accuracy like a fire drill. Count everything the week before month-end, patch whatever didn't match, submit the report, forget about it until next month. It worked, technically. Once. Then the small gaps started piling up faster than I could explain them. What actually changed things wasn't a new tool or a new SOP. It was realizing IRA isn't something you report on — it's something you either protect every day or you don't. Every goods receipt, every issue, every transfer is a moment where the system and the actual shelf can quietly drift apart. Catch that drift the same day and it's a two-minute fix. Let it sit for three weeks and it turns into a full investigation, and usually nobody remembers what actually happened. A few things I've genuinely stuck to since then: Reconcile the same day, not at month-end. I know it sounds obvious written down, but most warehouses don't actually do this — batching corrections is just easier in the moment. Let SAP flag mismatches early instead of waiting for someone to physically count and notice. The system usually knows before the floor does. Ask what kind of discrepancy it is before writing it off — receiving error, system delay, handling mistake. They all look the same on a report and none of them are fixed the same way. Whoever touched the transaction is the one who catches the error. Not an audit team three weeks later going through paperwork. None of this is glamorous. It's mostly just refusing to let small things wait. But it's the reason we held 100% month-end IRA consistently, and it's also the reason the number actually meant something when auditors came through — not just a figure that looked clean on a slide. If there's one thing 7 years taught me, it's that inventory accuracy was never really about the count. It was about how disciplined the process stayed on the days nobody was watching. #InventoryManagement #SupplyChain #FMCG
0
28
Customer Success & CX Operations | SaaS & eCommerce
$10k+
Earned
2x
Hired
5.0
Rating
20
Followers
Customer Success & CX Operations | SaaS & eCommerce
Motion Graphics Director - 3D Motion Designer
$10k+
Earned
6x
Hired
5.0
Rating
57
Followers
Motion Graphics Director - 3D Motion Designer
API Integration & Web Application Developer
$1k+
Earned
2x
Hired
12
Followers
API Integration & Web Application Developer
Cover image for From ACH to Card Payments:
From ACH to Card Payments: Building Scalable Payment Systems for US Businesses Over the past few years, I’ve worked closely with US-based businesses to design and implement secure, scalable payment systems across ACH, online card payments, and card-present (terminal) environments. My experience spans platforms like North.com (http://North.com), NMI, and other payment APIs—supporting everything from recurring ACH billing to fully integrated in-person payment solutions using physical terminals. On the ACH side, I’ve handled bank account verification, transaction lifecycles, and returns such as NSF and failed debits. ACH systems require careful management of delayed settlements, webhook events, and reconciliation—especially within US financial workflows. For online card payments, I’ve implemented secure gateways, tokenization, and optimized checkout experiences to ensure fast, seamless, and PCI-compliant transactions. I’ve also built and deployed card-present solutions, including: – EMV terminal integrations – Tap, dip, and swipe transaction flows – Device configuration and deployment – Real-time syncing with backend systems – Handling reversals, refunds, and partial approvals A critical part of every integration is compliance and security. My work ensures: – PCI DSS compliance for card data protection – Tokenization (no sensitive data storage) – Secure API authentication and encryption – Reliable webhook handling and audit-ready transaction logs From a technical perspective, I specialize in building robust API integrations, webhook listeners, retry mechanisms, and fail-safe systems that continue to operate reliably under real-world conditions. Key solutions I’ve delivered: – ACH debit and recurring billing systems – Online card payment integrations with secure token flows – Card-present terminal integrations – Real-time transaction systems using webhooks – Payment failure handling and reconciliation logic – CRM and internal dashboard integrations Working in the US payments ecosystem has given me deep exposure to compliance requirements, operational challenges, and the importance of building systems that are both secure and scalable. My focus is simple: build payment systems that are reliable, compliant, and seamless—whether online or in-person. Open to collaborations in fintech, payments, and API integrations.
1
118
Fractional PO/PM — 40+ projects, from MVPs to enterprise
2x
Hired
5.0
Rating
8
Followers
Fractional PO/PM — 40+ projects, from MVPs to enterprise
Startup SaaS & AI Systems Architect | MVP & Mobile Apps
5.0
Rating
12
Followers
Startup SaaS & AI Systems Architect | MVP & Mobile Apps
✧ Energy is my currency ✧
$10k+
Earned
4x
Hired
28
Followers
✧ Energy is my currency ✧