SOS Inventory and how it works with QB

Welcome to the Community, SGIBookkeeper. Let me provide some guidance about your concerns with inventory discrepancies when syncing data from the SOS app with QuickBooks Online.

After checking our records, I could not find any other reports or active alerts about this specific issue. It appears to be an isolated incident at the moment.

It's important to note that when integrating a third-party app like SOS, the information displayed in QBO entirely depends on the data shared and synced over from that external application.

I understand you have previously reached out to the SOS support team about the discrepancy. However, I would recommend contacting their support again to do a deeper investigation.

The SOS team can review the cost assembly amounts and inventory valuations on their end. They can also identify any settings or data mappings within the SOS platform that could be inadvertently inflating or duplicating the assembly costs when that data syncs to QBO.

Allow me to share additional resources related to managing third-party app integrations within QuickBooks Online: 

• Transfer App Ownership Or Disconnect Apps 
• Disconnect An App And Change Subscription 

Let me know if you need any other assistance from our side after consulting SOS support again, SGIBookkeeper. Additionally, you're always welcome to revisit the Community forum if you have any other questions as you continue getting familiar with working in the QBO platform. 

@SGIBookkeeper 

The feature in SOS is limited for a manufacturing company. Consider to replace it with a manufacturing app to integrate with QBO.

I get if you’re frustrated with the cost issues between SOS Inventory and Quickbooks. Seems like there’s some translation problem between the two systems. First, you might wanna double-check how those mappings are set up between SOS and quickbooks. Any mix-up could be why costs appear inflated or duplicated, ya know?

One idea is to dig into those integration settings for detailed cost allocation. SOS might be sending cost data in a way or currency that Quickbooks isn’t getting right. Try isolating a single assembly record and follow its trail from SOS to Quickbooks to see where the issue pops up.

Also, if you're using some batch or manual sync, check if there's a pattern or a specific time this issue pops up more. Keep an eye on those logs, unexpected errors tend to hide there. If SOS isn’t super helpful, maybe loop in a consultant who’s handled these integrations before. Sometimes, an extra pair of eyes is what you need. Also, since you're new in the role, doing a little check on recent transactions could help catch anything that’s been off since day one.