Inventory Management without 1С: Cloud Services and POS Software

"Do we need 1С?" is a question a small shop or cafe asks itself at the start and then periodically revisits as it grows. Between "keeping stock in a notebook" and "buying a full 1С license with an integrator," there is a whole class of cloud inventory management services and built-in POS software — let's break down when they are enough, and when you really need 1С.

1. Is 1С mandatory for a small store?#

No. For most small outlets — one or two stores, a simple product range, without complex production cost accounting — cloud inventory management services (such as MoySklad, Kontur.Market, and similar solutions) or the built-in inventory tracking of the POS software itself are sufficient: they cover stock balances, receipts, write-offs, basic sales analytics, and POS integration without a separate 1С license and without a database administrator.

1С becomes justified when a business already requires what is specifically designed for it: complex production accounting with multi-level cost calculations, multiple legal entities with complex inter-company document flow, or when the company's accounting is tied to 1С:Accounting and requires direct synchronization from there (see "POS and 1С"). For typical retail or foodservice, this is a result of scaling, not a starting requirement.

2. How to Connect a POS System with Cloud Inventory Management#

Connecting a POS system with an external cloud service is usually built via API or a ready-made integration, rather than manual file transfer:

1. Product catalog — items, categories, and barcodes are synchronized from inventory management to the POS (or vice versa if the catalog is managed directly on the POS) — usually on a schedule or manually by pressing a button, rather than in real time.
2. Prices — when a price changes in inventory management, the POS must fetch the new value during the next sync; the frequency — from "instantly" (webhook/API) to "once a day" — depends on the specific integration.
3. Stock levels — deductions upon sale usually occur in real time or in short batches (minutes) rather than once a day — otherwise, the POS risks offering an item that is already out of stock.

Synchronization frequency is not an abstract parameter: once a day is usually enough for prices, while for stock levels of high-turnover items (perishables, popular items), near-real-time synchronization is better; otherwise, the cashier sells what is no longer on the shelf.

3. EGAIS and Marking in Cloud Services Without 1С#

Both tracks are technically not tied to 1С — they operate through separate mandatory modules that any system can connect, including cloud inventory management or POS:

• EGAIS — registration does not come directly from inventory control, but through a local UTM (Universal Transport Module) accessed by the POS/accounting software; 1С is not mandatory in this chain; for a detailed breakdown of the scheme, see the article "EGAIS at the Checkout".
• "Chestny ZNAK" marking — also a separate track: scanning Data Matrix, verifying the code via OSU/GIS MT, and transmitting attributes to the receipt can be done by any system supporting FFD 1.2 and the required FN-M, regardless of whether it is 1С or a cloud service (see "Marking at the Checkout").

In practice, not every cloud service supports these modules "out of the box" — check with your provider regarding integration with UTM and GIS MT mode for your product groups before making the switch.

4. Migration from 1С to a Cloud Service and Back#

Data transfer between systems is primarily a matter of moving two things: the product catalog (items, barcodes, prices, categories) and current stock levels as of the migration date.

1. Export the item catalog from the old system — usually in CSV/Excel; the key matching field is the barcode or SKU, not just the name (names often differ in spelling between systems).
2. Import into the new system — most cloud services and POS systems accept spreadsheet imports directly or via AI price list parsing (in Cenaly — see Section 9).
3. Record stock levels as of a specific date and time — conduct (or schedule) an inventory stocktake in the old system right before switching over, so the new system starts with reliable numbers rather than months of accumulated error.
4. Do not run both systems in parallel longer than the transition period — inventory discrepancies between "old" and "new" records grow with every day of double entry and will later require a separate inventory reconciliation (Section 7).

Reverse migration (from a cloud service to 1С) works the exact same way — the roles are simply reversed.

5. PC POS Software vs. Smart POS with Built-in Inventory#

A detailed comparison of hardware classes (push-button standalone cash register, smart terminal, fiscal recorder + POS) can be found in the article "How to Choose an Online POS".

6. POS and Inventory Data Exchange: Common Pitfalls#

• Different units of measure — "pcs." in one system and "pack" in another for the same item result in multi-fold stock discrepancies; verify units during the initial integration setup.
• Duplicate items — if matching is based on the name rather than a persistent identifier (barcode, ID), re-synchronization may create a second item card instead of updating the existing one.
• Offline queue at the POS. When the connection is lost, sales must accumulate locally and be sent upon restoration — otherwise, inventory deduction for the offline period is lost.
• Price sync delay. The cashier sees the old price if the integration updates once a day and the price was changed just now — check the synchronization schedule specifically for prices.

7. Stocktaking with a scanner and POS without stopping sales#

A full store shutdown for an "inventory count" isn't always necessary — here is the procedure for a location that continues serving customers during the count:

1. Divide the area into zones and count one at a time rather than the entire store at once — sales in an already recounted zone do not affect the stocktaking total if you fix a snapshot time for that zone.
2. Scan barcodes with a scanner instead of entering quantities manually — this is significantly faster and virtually eliminates typos in the item code.
3. Record the actual quantity for each dish/item in a separate stocktaking document without touching current sales — the system will automatically reconcile the physical count against the calculated stock balance at the snapshot time.
4. Sales during the count in an already counted zone are accounted for as standard write-offs — they simply shouldn't be included in the stock balance that you are physically recounting right now.
5. Final discrepancies are processed as a standard shortage/surplus — not via a correction receipt (a correction receipt closes an unrecorded transaction for tax authorities, not lost or extra stock in inventory).

8. Example#

A cosmetics store with two locations kept records in a thick notebook and missed items when placing supplier orders. They switched to cloud inventory management: exported the product list from their old POS software by barcodes, uploaded it to the new service, and conducted a control stocktaking across both locations in a single evening using a scanner. The POS registers at both locations were connected to the inventory management system via API with real-time stock synchronization and price updates once a day. A month later, the owner confirmed that discrepancies between purchases and actual stock levels were reduced — supplier orders are now placed based on actual reorder points rather than "by eye."

9. How to do this in Cenaly#

• The built-in inventory and stock management in Cenaly does not require a separate 1С or external cloud service: stock balances, receiving, write-offs based on dish recipes, and purchasing are managed directly within the same platform as the POS — without additional synchronization between systems.
• You can populate the catalog using AI price list import — Excel, Word, PDF, or even a photo — instead of manually transferring items during migration.
• Stocktaking with a scanner — action "+ Operations" → "Stocktaking" in the Inventory section: the form is pre-filled with current stock balances, the scanner speeds up searching for items, and sales of items not yet recounted continue as normal.
• If inventory management is still kept in 1С:Accounting, a separate integration synchronizes items and suppliers via OData — see "1С:Accounting — integration"; this does not require transferring all accounting to Cenaly all at once.
• Receipt printing on a physical fiscal register, if used, is handled via Cenaly Hardware Bridge, regardless of where inventory is managed.

10. Frequently Asked Questions#

Can a cloud inventory management service handle EGAIS for beer without 1С? Yes, if the provider supports integration with UTM — 1С is not the only way to connect to EGAIS, the mechanism works via UTM independently of the accounting system (section 3).

How do you know it's time to switch from a cloud service to 1С, and not the other way around? When accounting hits a wall with complex manufacturing cost calculation, multiple legal entities with internal document management, or an accounting department requirement to use specifically 1С — these are signals to switch, rather than revenue size itself.

What to do if duplicate items appeared after integration? Check which field the system uses to match items — if by name rather than barcode/ID, switch the matching to a unique identifier and merge the duplicates.

Is it mandatory to perform physical inventory with a complete sales halt? No, by dividing into zones and capturing a snapshot for each zone separately, the store can continue serving customers (section 7).

Related articles: inventory in Cenaly · AI catalog import · POS and 1С · EGAIS at POS · product labeling at POS

This material is for reference purposes only and does not replace consultation with an accountant or an inventory management system integrator. Primary sources: Federal Law No. 54-FZ "On the Use of Cash Registers", Federal Law No. 171-FZ (regulation of the alcohol market and EGAIS), methodological guidelines on product labeling (chestnyznak.rf), 1С:Enterprise documentation.