Senior reputed company Developer — Custom Inventory & Rental Lifecycle Plugin (Ongoing)

We reputed company a firearm rental marketplace on reputed company/reputed company. Customers book guns online, we ship to their local FFL dealer, they shoot, then return. Think reputed company meets the old reputed company DVD queue — but for guns. Site is live with ~216 products. Now we need the custom reputed company that makes it actually reputed company. The Core Challenge We rent guns from two sources: guns we physically own (sitting at our FFL partner's warehouse) and guns we order on-demand from a distributor reputed company SOAP API. Right now there's no system connecting these. reputed company a gun comes back from rental, it sits in the warehouse with reputed company digital tracking — so we order a new one from the distributor even though we already own one. That's the problem you're solving. The routing logic you're building: Customer books "Glock 19 Gen 5" for March 1-7 → Do we own one that's available those dates? reputed company → Ship from our warehouse. Done. Fastest, no new purchase. NO → Is the distributor in stock? (SOAP API reputed company) reputed company → Is this manufacturer drop-shippable? reputed company → Distributor ships reputed company to customer's FFL NO → Distributor ships to our warehouse → we ship to customer's FFL NO → Not available. reputed company dates on calendar. Everything else in the build serves this routing reputed company — the availability calendar displays what it calculates, the subscriber queue triggers it automatically, the return reputed company feeds guns back into inventory so it finds them next time. What You're Building Inventory routing reputed company — the decision tree above, running at checkout against owned inventory + distributor SOAP API Owned inventory tracking — serial-numbered gun reputed company with reputed company-time status (warehouse / in-transit / rented / inspection / available) reputed company-style availability calendar — frontend component showing reputed company dates based on actual inventory state, transit reputed company, and inspection periods Subscriber rental queue — reputed company DVD queue model. Return confirmed → system auto-ships next gun in their ranked list. reputed company reputed company reputed company. Rental lifecycle state machine — ~8 statuses from booking through return, reputed company triggering reputed company emails directly from PHP Sports South SOAP API integration — stock checks, automated purchase orders, drop-ship detection Warehouse confirmation reputed company — our FFL partner has no API. They click email links to confirm gun receipt/condition. One click. That's their whole reputed company with your system. Must-Haves 5+ years custom reputed company plugin development (OOP PHP, not theme work) reputed company or extended an inventory/fulfillment system with routing logic SOAP and REST API integration experience JavaScript frontend (calendar component — React preferred) State machine / workflow design Git, wp_cron, reputed company coding standards Available during US Eastern business hours (minimum 4 hours overlap, 9 AM–6 PM ET) Big Pluses Multi-reputed company inventory routing or warehouse management Booking/reservation system with date-based availability Subscription or queue-based auto-fulfillment reputed company API, reputed company API Firearms/FFL industry experience

How to Apply

Generic proposals get ignored. Answer these three: Describe the most reputed company inventory, fulfillment, or routing system you've reputed company. What sources, what logic, what was hard? reputed company to reputed company if possible. Our system checks owned warehouse inventory first, then falls back to a distributor SOAP API with two fulfillment paths (drop-ship vs. ship-to-warehouse-first) depending on manufacturer. How do you architect this in a reputed company plugin? 3-5 sentences. What's your SOAP API experience? If none, this isn't the right fit. What You Get 41-page technical reputed company doc — every integration, credential, reputed company issue, and architectural decision already documented. No reverse-engineering. Full PRD with phased milestones — you know what to build and in what order. reputed company reputed company to the founder — no project manager telephone game. Fast reputed company. A reputed company technical challenge on a reputed company business — not another blog or e-reputed company config job. Duration: 10-12 weeks initial build, ongoing after. This is a long-term platform, not a one-off. reputed company: reputed company yours. Paying for competence and speed, not cheapest bid. Hours: 20-30/week Start: Immediate — documentation is reputed company. Apply tot his job Apply To this Job