Hi Rusty, are you still looking for help with the SOS Inventory work-order sync? I’d start by inspecting the failed write-back step and testing one work order in your SOS sandbox. Could you share the failing Make module and a redacted error response, with tokens and customer data removed? I’ll assess whether I can resolve that specific issue and propose a fixed scope and price before any paid work. The proposed deliverable would include the agreed fix, a repeatable test, and short maintenance notes. I use AI-assisted debugging and verify results with tests.
Hi Rusty, just wanted to check if you’re still having trouble with the SOS Inventory write-back. If you haven’t got it sorted yet, would you be open to a short paid diagnostic to figure out what’s causing it???
Your concern about the team being helpless when one system changes is valid. The first goal should be to isolate the failed SOS Inventory write-back and document it clearly—not rebuild the Sales Order side that already works.
My strongest hands-on work is with n8n, inventory reconciliation, REST APIs, Google Sheets, duplicate prevention, validation and error handling. I haven’t completed a client project using this exact Make + SOS Inventory combination, so I’d start with a small fixed diagnostic instead of overstating experience.
For $75, I would:
• Review the failed Make module using a sanitized request and response
• Determine whether the blocker is trial-account permissions, authentication, payload structure or workflow logic
• Test one minimal Work Order creation path in the SOS sandbox
• Provide the exact repair scope and maintenance checks
If the write path works, the $75 would be credited toward the implementation. No credentials or live customer data should be posted publicly.