One stock truth across channels

Sell everywhere without maintaining different versions of your stock.

A shop sale, website order, WhatsApp order, and branch sale should not force the owner to reconcile four stock lists. IGFirstERP keeps each recorded sale tied to the relevant product, unit, variation, location, customer, payment, and fulfilment path so availability can follow one controlled inventory truth.

Channels are where customers buy. Inventory authority is where the business proves what remains available and why it changed.

Find my plan Book an Operations Fit Call

Published 2026-07-11 · Verified 2026-07-11 · Editorial policy

Decision points before a demo

What the owner needs to know

What record is created?

Each recorded sale or order retains channel, location, product, variation, unit, quantity, customer, user, payment, and fulfilment context where configured.

What else changes?

The relevant inventory position and connected availability views reflect the sale according to the configured channel and location rules.

What can management verify?

Managers can review order source, stock effect, mapping, payment, fulfilment, exceptions, and reconciliation status instead of trusting channel totals alone.

Best fit

  • Retailers selling from a physical location and a native IGFirstERP storefront.
  • Businesses connecting an existing WooCommerce store to controlled ERP inventory.
  • Teams receiving WhatsApp or social-originated orders that need to become proper sales records.

Probably not fit yet

  • Treating Instagram or TikTok as a verified native inventory integration without an implemented connector.
  • Selling from a channel that is not mapped to the correct product, variation, unit, or location.
  • Assuming connectivity and third-party webhooks can never fail.

Why it returns

Every separate stock list eventually disagrees

Channels move at different speeds. Walk-in sales happen quickly, website orders can reserve stock, and chat orders may sit outside the system. Without one authority, staff spend the day confirming the same quantity repeatedly.

  • Record channel-originated orders in the operating system.
  • Map the correct product, variation, unit, and location.
  • Use availability and reservation rules consistently.

Native or connected

Use the storefront path that matches the business

A business can use the native IGFirstERP storefront or keep an existing WooCommerce site. Both paths need clear store identity, product scope, location authority, monitoring, and recovery.

  • Use native storefront controls for a new IGFirstERP website.
  • Use the WooCommerce recovery page for an existing Woo store.
  • Keep the ERP record as the operating evidence behind the channel.

Owner control

Do not stop at “sync is on”

The owner needs evidence that orders, availability, payments, and fulfilment agree—and a way to see what needs repair when they do not.

  • Review failed or delayed channel work.
  • Reconcile order and stock differences.
  • Keep fulfilment and customer follow-up attached to the order.

Demonstration workflow · not customer data

Follow one product across a shop and storefront

Demonstration data uses one product with variants, one location, POS availability, and a configured online storefront.

Step 1

Confirm the stock authority

Set the location, product, variation, unit, and available quantity the channel should obey.

Step 2

Record a shop sale

Complete the POS sale and retain the user, customer, payment, and stock effect.

Step 3

Review online availability

Verify that the configured storefront now reads the remaining controlled availability.

Step 4

Investigate disagreement

Use mapping, queue, health, reconciliation, or correction paths when records do not align.

What the owner can verify

  • Every channel points to an explicit location and product identity.
  • The sale record explains the inventory effect and responsible user.
  • Exceptions, holds, retries, and reconciliation remain reviewable where supported.

When the happy path fails

  • Native storefront readiness exposes incomplete product, payment, shipping, or domain setup.
  • WooCommerce flows retain mapping, health, hold, retry, and reconciliation paths.
  • Chat or social-originated orders must be recorded before they can participate in stock truth.

Explicit limitations

What this page does not promise

  • Actual timing depends on channel configuration, reservations, connectivity, providers, webhooks, and queue health.
  • Instagram and TikTok are not described as native stock integrations without separately verified connectors.
  • One stock truth still depends on staff recording off-platform sales and adjustments correctly.

Operational proof, not vanity claims

These proof assets show what became visible, traceable, faster, or easier to review after IGFirstERP was implemented. Named customer metrics are used only where permission has been granted. Results vary by operating discipline, data quality, implementation scope, and adoption.

Proof library Named customer evidence Review what became traceable, visible, or easier to control, with limitations stated. Methodology How claims are governed See the evidence, permission, review-date, and limitation rules behind public claims. Product Walk through the operating system See how stock, sales, staff, storefronts, and reporting connect.
Control hub Start from the operating problem Find the stock, staff, branch, website, or reporting problem that keeps returning. Academy Operator education Use practical lessons to strengthen the process around the system. Documentation Product guides and SOPs Review current operating instructions for IGFirstERP workflows.

Questions serious buyers ask

Can IGFirstERP connect physical and online sales?

Yes. The native storefront and configured POS can use the same operating inventory records, while existing WooCommerce stores use a separate mapping and recovery workflow.

Does IGFirstERP synchronise Instagram and TikTok inventory directly?

This page does not claim a native Instagram or TikTok inventory connector. Orders originating there must enter a supported IGFirstERP order or sales workflow to affect controlled stock.

What happens when a website update fails?

The exact recovery path depends on the storefront. WooCommerce supports mapping, health, hold, retry, and reconciliation controls; native storefront readiness exposes configuration gaps.

Operations Fit Call

Choose the path that fits your operation

Use Find my plan when the workflow is clear. Book an Operations Fit Call when locations, integrations, migration, permissions, or reporting need to be mapped first.

Book an Operations Fit Call