Accounting workflow automation

Bad Rules Break Books

Webgility lets you define how different orders, channels, SKUs, fees, and exceptions should post, so the right accounting logic runs before errors hit your books.

The Wrong Route, the Wrong Account

When an order routes incorrectly (wrong fulfillment path, wrong channel, wrong fee mapping) the accounting entry that follows is wrong. Not delayed. Wrong. It posts to whatever account is default. You find it at reconciliation if you're diligent. If you're not, it stays.

Routing error detected 3 wrong accounts
Order #AMZ-8841, FBA routed
Wrong COGS account · posted to "Warehouse COGS" not "FBA COGS"
Wrong account
Order #WH-0221, Wholesale
Revenue posted to DTC account · should be B2B Revenue
Wrong account
Webgility catches this before posting
Rule-based routing applied per order type · not default
Prevented

Routing Logic Has Accounting Consequences

Webgility's routing rules don't just move orders to the right warehouse. They determine which revenue account, which COGS account, and which fee category posts for each order. Shopify wholesale, FBA-routed, drop-shipped, and direct-fulfilled orders don't belong in the same account. Webgility enforces that distinction at the time of routing, before the entry is made.

Routing Rules Applied per order
Shopify DTC orderRevenue · DTC Sales
Amazon FBA orderCOGS · FBA Fulfillment
Wholesale net-30 POAR · B2B Receivables
Drop-ship orderRevenue · Drop-ship channel

Set once · enforced on every order from that point forward

Flagged Before It Posts

When an order can't be routed cleanly, address problem, out-of-stock SKU, payment hold, channel mismatch, Webgility holds it in exception state. It does not post a partial entry. It does not route to a default account. The order waits for resolution. The accounting waits with it.

Exception queue 2 held
Order #SH-7714: Address error
Can't route · held in exception state · no entry posted
Waiting for resolution, not in catch-all account
Held
Order #AMZ-5521: Unrecognized SKU
No item mapping found · held for review
Partial entry not posted · accounting waits with order
Held

A Return Has Three Steps

The item has to post back to inventory. The refund has to hit the correct account, not the original revenue line, and not a generic returns bucket. The customer record has to update. If any of those three don't happen, your inventory count, your margin, and your receivables are each carrying an error. Webgility completes all three before the return closes.

Return #RMA-8842: All 3 steps Complete
Step 1 · Inventory restored
Item posted back to warehouse location · QuickBooks updated
✓ Done
Step 2 · Refund entry posted
Revenue contra account, not original revenue reversal
✓ Done
Step 3 · Customer record updated
Receivables cleared · account balance correct
✓ Done
Explore Sandbox  ·  No Signup Required

See Webgility in Action.

A real instance pre-loaded with sample orders, channels, and accounting entries. Nothing to install. No account needed.

🔒 my-sandbox.webgility.com
Online
CONTACT SALES
PREVIEW MODE
S Shopify Store
Open the Sandbox
Free to explore  ·  No account needed  ·  Sample data only
The Demo

Find out what your operational gaps are actually costing you.

Our team of experts will help surface your operations and finance concerns. In 30 minutes, we will discuss your channels, accounting setup, leakages, inventory inconsistencies, and close process.

Operational Snapshot ● Live
Orders reconciled today 1,247 ✓
Amazon payout tied out $47,241 ✓
Exceptions resolved 3 cleared
Inventory synced All channels ✓
Books status Certified ✓