SABSUS Lesson: Import Products and Set Up Inventory
A setup lesson for importing products, SKUs, categories, units, suppliers, purchase prices and stock rules in SABSUS.
Set up products, categories, units, suppliers, stock rules and purchase data before the team starts using the system daily.
Short answer
Set up products, categories, units, suppliers, stock rules and purchase data before the team starts using the system daily.
A messy catalog creates errors in POS, ordering, inventory, delivery, analytics and customer app pages.
Goal of the lesson
By the end of this lesson, the business should have a clean product base that can support POS sales, online ordering, stock tracking, supplier receiving and analytics.
The goal is not only import speed. The goal is operational accuracy.
Prepare the source file
Before import, clean product names, categories, units, SKU/barcode fields, sale price, tax settings, supplier names, purchase prices and opening stock.
Do not import old spreadsheet chaos into the new system. Use the migration as a cleanup moment.
Check units and categories
Units affect inventory math. A product sold as one item may be purchased by case, weight or package. Categories affect reporting, menus, customer app navigation and SEO pages.
Make these decisions before the first import when possible.
Quality check after import
Open sample products and verify price, unit, stock, category, image, supplier and availability. Then run a test order to confirm stock changes correctly.
If the test order fails, fix the catalog before inviting the full team.
Implementation checklist
- Clean product names
- Categories and units defined
- SKU/barcode fields checked
- Supplier and purchase price linked
- Test order updates stock
Common mistakes to avoid
- Publishing a page before it answers a real buyer or operator question.
- Using broad claims without showing the workflow, data or module that supports the claim.
- Letting metadata, schema and visible page text describe different things.
- Creating isolated content that does not link to related SABSUS modules, lessons or comparison pages.
- Measuring the page only by visits instead of the action it should create: demo request, call, order, booking, setup step or internal handoff.
Content assets to add next
The page becomes stronger when it is supported by real product and operational proof. Add screenshots, process examples, checklists, before-and-after states, or short clips when they help the reader understand what happens in the business.
For Lesson content, the most useful asset is usually not decoration. It is a concrete view of the workflow: an order status screen, a customer profile, an inventory change, a delivery assignment, a booking slot, a white-label app screen or an owner dashboard.
| Asset | Why it helps |
|---|---|
| Screenshot or workflow image | Shows that the concept is attached to a real system, not only a marketing claim. |
| Checklist | Turns the article into a practical operator resource that can be used during setup. |
| Comparison criteria | Helps buyers and AI systems understand when SABSUS is a fit and when another tool may be enough. |
| FAQ | Answers the exact doubts that block a buyer, owner or implementation team from taking the next step. |
Measurement and next actions
After publishing this page, check whether it is discoverable through internal links, present in the sitemap and represented in content-index.json. The page should also be reachable from at least one hub and one relevant product or module page.
Search Console should be used to watch impressions, query variants and click behavior. Analytics should watch whether users continue to the related SABSUS page, demo request, contact section, pricing page, customer app page or module page. If the page attracts impressions but not actions, the next edit should improve the above-the-fold answer and the internal call to action.
The next content pass should compare this page against the top competing results for the target query. Look for missing buyer criteria, screenshots, FAQ questions, examples, schema and internal links. Add only what makes the page more useful and more specific.
How SABSUS connects this to operations
| Layer | What it should prove |
|---|---|
| Customer and order data | The page should connect search, app, POS, CRM and order history instead of treating them as separate systems. |
| Inventory and fulfillment | The promise on the page should match actual availability, status updates, staff tasks and delivery capacity. |
| Owner control | The owner should be able to review results through reports, analytics, tasks, exceptions and repeat customer behavior. |
Related SABSUS pages
FAQ
Who is this page for?
It is for new SABSUS operators setting up catalog and stock.
What should be fixed first?
A messy catalog creates errors in POS, ordering, inventory, delivery, analytics and customer app pages.
What is the SABSUS approach?
Set up products, categories, units, suppliers, stock rules and purchase data before the team starts using the system daily.