What is SIOCS?

Store Inventory Operations Cloud Service (SIOCS) — formerly known as Store Inventory Management (SIM) — is Oracle's mobile inventory management platform for retail stores. While RMS manages inventory at the enterprise level (what the system thinks is in each store), SIOCS gives store associates the tools to manage inventory at the physical level (what is actually on the shelf and in the backroom).

The key difference between SIOCS and RMS is perspective: RMS is the financial truth (what the books say), while SIOCS is the physical truth (what's actually in the building). When these two diverge, the retailer has an inventory accuracy problem.

Mobile-First Architecture

SIOCS is designed to run on handheld mobile devices (ruggedized scanners, tablets, smartphones) that store associates carry on the sales floor. The architecture is:

Application Tiers

┌──────────────┐     ┌──────────────┐     ┌──────────────┐     ┌──────────┐
│   Mobile     │────▶│   SIOCS      │────▶│   RIB        │────▶│   RMS    │
│   Device     │     │   Server     │     │  (Message    │     │          │
│  (Scanner/   │     │  (In-Store)  │     │   Bus)       │     │(Enterprise│
│   Tablet)    │     │              │     │              │     │  Master) │
│              │     │ Local DB     │     │              │     │          │
│  HTML5 UI    │     │ + Business   │     │ Publishes    │     │ Updates  │
│  or Native   │     │   Logic      │     │ Inventory    │     │ SOH,     │
│  App         │     │              │     │ Messages     │     │ Ledger   │
└──────────────┘     └──────────────┘     └──────────────┘     └──────────┘

• Mobile Device: Runs a web-based (HTML5) or native application with barcode scanning capability. Connects to the SIOCS server over the store's local WiFi network.
• SIOCS Server: Runs in the store (or hosted centrally in cloud deployments) with a local database containing the store's item master, inventory positions, and pending operations.
• RIB Integration: All completed operations (receipts, counts, transfers) are published to the Retail Integration Bus for consumption by RMS.

The Receiving Workflow

When a truck arrives at the store's receiving dock, a store associate uses SIOCS to verify and record the delivery.

The Process

1. Scan the ASN (Advance Shipment Notice): The delivery arrives with a unique shipment ID. The associate scans the barcode on the delivery paperwork, which pulls up the expected contents from the ASN that was sent ahead by the warehouse.

2. Verify Contents: The associate scans each carton or individual item. SIOCS compares the scanned items against the ASN:

   • ✅ Expected item scanned — quantity incremented
   • ⚠️ Unexpected item scanned — flagged as overage
   • ❌ Expected item NOT scanned — flagged as shortage

3. Record Damages: If any items arrive damaged, the associate records the damage in SIOCS with a reason code (crushed carton, water damage, etc.).

4. Confirm Receipt: The associate confirms the receipt. SIOCS generates a Receipt Confirmation Message that is published to RMS via RIB.

5. RMS Impact: Upon receiving the message, RMS:

   • Increases ITEM_LOC_SOH.STOCK_ON_HAND for the receiving store
   • Decreases ITEM_LOC_SOH.IN_TRANSIT_QTY
   • Posts a financial receipt entry to the STOCK_LEDGER

Stock Counts & Cycle Counting

Inventory accuracy degrades over time due to theft (shrinkage), miscounts, damage, and administrative errors. Stock counts are the correction mechanism.

Types of Counts

1. Full Physical Inventory Count: The entire store is counted. Every item in every location (sales floor, backroom, fitting rooms, display fixtures) is scanned and counted. This typically happens 1–2 times per year and often requires the store to close for 12–24 hours.

2. Cycle Count: A targeted count of a subset of items. Cycle counts are performed regularly (weekly or daily) and focus on high-value items, items with known discrepancy patterns, or items flagged by exception reports. The store remains open during cycle counts.

3. Problem Line Count: After a full inventory count, any items with significant variances (counted quantity vs. system quantity) are re-counted to confirm accuracy before adjustments are posted.

Count Workflow

1. HQ schedules a count — RMS creates a stock count header and sends it to SIOCS via RIB
2. SIOCS creates the count document with the list of items/locations to be counted
3. Associates scan and count using mobile devices
4. Supervisor reviews variances — items where counted quantity differs significantly from system quantity
5. Count is authorized — the supervisor approves the final counted quantities
6. Adjustment posted to RMS — SIOCS sends an inventory adjustment message to RMS, which updates STOCK_ON_HAND and posts the adjustment to the STOCK_LEDGER

-- Find items with significant SOH discrepancies 
-- (system thinks we have stock, but sales suggest we don't)
SELECT 
    ils.item,
    ils.loc       AS store,
    ils.stock_on_hand,
    NVL(ilh.total_sold_last_30d, 0) AS sold_last_30_days,
    CASE 
        WHEN ils.stock_on_hand > 0 
             AND NVL(ilh.total_sold_last_30d, 0) = 0 
        THEN 'PHANTOM_STOCK'
        WHEN ils.stock_on_hand <= 0 
             AND NVL(ilh.total_sold_last_30d, 0) > 0 
        THEN 'NEGATIVE_SOH_WITH_SALES'
        ELSE 'REVIEW'
    END AS discrepancy_type
FROM 
    item_loc_soh ils
LEFT JOIN (
    SELECT item, loc, SUM(sales_qty) AS total_sold_last_30d
    FROM item_loc_hist
    WHERE end_date >= TRUNC(SYSDATE) - 30
    GROUP BY item, loc
) ilh ON ils.item = ilh.item AND ils.loc = ilh.loc
WHERE 
    ils.loc_type = 'S'
    AND (
        (ils.stock_on_hand > 10 AND NVL(ilh.total_sold_last_30d, 0) = 0)
        OR ils.stock_on_hand < 0
    )
ORDER BY 
    ils.stock_on_hand DESC;

Store Transfers

SIOCS manages the creation and processing of store-to-store transfers. When one store has excess inventory and another store needs it:

1. Transfer Request: A store manager creates a transfer request in SIOCS specifying which items and quantities to send.
2. Approval: The transfer may require district manager approval depending on the value.
3. Pick & Pack: The sending store associate picks the items, scans them in SIOCS, and packs them for shipment.
4. Ship Confirmation: The sending store confirms the shipment. RMS reduces STOCK_ON_HAND at the sending store and increases IN_TRANSIT_QTY at the receiving store.
5. Receive: The receiving store receives the transfer using the same receiving workflow described above.

Item Lookup & Inventory Inquiry

One of the most-used features by store associates is Item Lookup. When a customer asks "Do you have this in a size 8?", the associate can:

1. Scan the item on their mobile device
2. See the current store's inventory (sales floor + backroom)
3. Check nearby stores for available stock
4. Check warehouse availability for potential ship-to-store
5. Create a customer order if the item is not available locally but exists elsewhere

Integration with RMS

Because RMS is the financial master, SIOCS must stay in perfect sync. Every physical operation in SIOCS generates a corresponding financial update in RMS:

SIOCS Data Model Concepts

SIOCS maintains its own local data model that mirrors a subset of RMS:

Operational Best Practices