🖥️📱 Part 3

Desktop & Mobile — who does what

Rather than a correspondence table, here are five typical days in an artisan workshop. You'll naturally see when each team member switches from one interface to the other, and why.

⏱ Reading ~8 min
·
5 illustrated scenarios
·
Admin + Operator
🖥️
Interface desktop Web browser — BigCommerce or Shopify admin
Procurement
  • Materials stock
  • Suppliers
  • Supply orders (purchase orders)
Production
  • Production runs
  • Recipes
Sales & B2B
  • Products & stock
  • Resellers
  • B2B orders
Management
  • Alerts
  • Reports
Configuration
  • Workshops & warehouses
  • Data import
  • Users
📱
Interface mobile Phone browser — /mobile
Bottom navigation bar
  • Dashboard — daily summary
  • Stock — view & adjustment
  • Manufacturing — planned & ongoing runs
  • Procurement — orders to receive
  • Orders — B2B dispatch & tracking
At the top of each screen
  • Active warehouse selector
  • Active alerts banner
Action performed on desktop (admin)
Action performed on mobile (operator)
Automatic action triggered by MakerStocks
🖥️ Scenario 3.1 — Desktop only

Monday morning — the manager starts her week

Sophie, the workshop manager, opens MakerStocks from her desk before going down to production. She has 20 minutes to take stock before planning the week.

D
Sophie — Admin Management → Alerts
Check the alerts dashboard
The home page shows all active alerts, refreshed every 30 seconds: low stock on beeswax (threshold 5 kg, current stock 3.2 kg), and a run scheduled last week still blocked for lack of stock. She acknowledges the non-critical alerts.
D
Sophie — Admin Procurement → Materials stock
Check the critical stock details
She opens the beeswax record. She reviews the movement history for the last 30 days: consumption has accelerated this week. She manually raises the alert threshold from 5 to 8 kg to reflect the new pace.
D
Sophie — Admin Procurement → Supply orders
Create a supplier purchase order
She creates a purchase order with her usual supplier: 20 kg of wax, 5 L of coconut oil. She enters the expected delivery date (Thursday) and sends the order with status Sent. The supplier will receive the order by email.
Pro+
D
Sophie — Admin Production → Production runs
Schedule the week's runs
She schedules 3 runs: 4 batches of Vanilla Candle for Tuesday, 2 batches of Milk Soap for Wednesday, and 6 batches of Fig Candle for Friday (once the wax is received). Tuesday's and Wednesday's runs switch to Planned status immediately since stock is sufficient.
In 20 minutes, Sophie has everything sorted out. The operators will find their runs waiting on mobile as soon as they arrive at the workshop. She didn't have to send them a single message.

📱 Scenario 3.2 — Mobile only

Surprise delivery — Thomas receives alone

Thomas is an operator. He is alone in the workshop on Thursday morning when the delivery driver arrives with the raw materials order. Sophie is in a meeting, unreachable. Thomas handles everything from his phone.

M
Thomas — Operator Mobile → Supply orders
Check orders pending receipt
Thomas opens the Supply orders tab on his phone. He sees the purchase order Sophie created on Monday, with status Sent, showing the expected items: 20 kg of beeswax and 5 L of coconut oil.
M
Thomas — Operator Mobile → Receiving
Open the receiving form and check off the lines
He taps "Receive" from the order card. The receiving screen shows each line of the order with the quantity ordered and the quantity already received (0). He checks off both received lines.
M
Thomas — Operator Mobile → Receiving — lot entry
Enter quantities, lot numbers and expiry dates
For the wax: he enters 19.8 kg received (the driver delivered slightly less), lot number CIR-2024-089, and expiry date 12/31/2026. For the oil: exactly 5 L, lot HCO-2024-012. He selects "Main Workshop" as the destination warehouse.
Lot traceability — Pro+
M
Thomas — Operator Mobile → Receiving
Confirm the receipt
He taps "Confirm receipt". A success message confirms it's been recorded. The order switches to Partially received status (since 0.2 kg of wax is missing).
MakerStocks automatic System
Stock updated, low-stock alert cleared
The 19.8 kg of wax is credited immediately to the selected warehouse, with the associated lot and expiry date. The low-stock alert on wax disappears from the dashboard. The run scheduled for Friday (blocked for lack of stock) can now be executed.
The entire receipt is tracked without Sophie ever leaving her meeting. When she reopens MakerStocks in the afternoon, the stock is up to date, the lots are recorded, and the alert has disappeared.

🖥️📱 Scenario 3.3 — Desktop + Mobile

Production day — the workshop runs at full capacity

Tuesday, Vanilla Candle production is scheduled. Sophie has planned 4 batches from the desktop. Thomas and his colleague Amina will execute them from their respective phones.

M
Thomas — Operator Mobile → Manufacturing → Planned tab
Check the day's runs
On arrival, Thomas opens the Manufacturing tab. He sees the "Vanilla Candle — 4 batches" run scheduled by Sophie. He checks the associated warehouse and reads Sophie's note: "Careful, weigh the wax with the precision scale".
M
Thomas — Operator Mobile → Manufacturing → Start button
Start the run
He taps "Start". The run switches to In progress status. The tab automatically switches to "In progress" so he can follow along.
MakerStocks automatic System
The run appears in real time on Sophie's desktop
In Production → Production runs, Sophie sees the run switch to In progress status without having done anything. She can follow the state of production from her desk.
D
Sophie — Admin Desktop → Production → Runs
Launch an extra unplanned run
Sophie realizes an urgent order needs 2 batches of Milk Soap immediately. She launches a run directly from the desktop (skipping the "Schedule" step): the system checks stock, calculates the estimated COGS, and executes.
M
Amina — Operator Mobile → Stock → material search
Check the batch before opening a bag
Amina isn't sure about a bag of wax: is it the right batch? She searches for the material from the Stock tab. MakerStocks displays the available stock, the matching batch and the expiry date. She confirms it's the right bag.
M
Thomas — Operator Mobile → Manufacturing → In progress tab
Complete the run at the end of the session
Two hours later, the 4 batches have been poured and are cooling. Thomas taps "Complete run". The system confirms: 48 candles produced (4 batches × 12 units), total COGS calculated.
MakerStocks automatic System
Materials deducted, finished goods stock credited, COGS recorded
The materials consumed (wax, wick, vanilla fragrance, container) are deducted from FIFO stock with traceability of the lots used. 48 units of "Vanilla Candle" are credited to finished goods stock. The unit COGS is calculated and recorded.
Sophie plans, Thomas and Amina execute — without ever crossing paths. Statuses update in real time on both sides. Everyone sees exactly what concerns them.

🖥️📱 Scenario 3.4 — Desktop + Mobile · Business plan

Reseller order — from creation to shipment

The shop "Les Petits Plaisirs" (B2B reseller) orders 24 vanilla candles and 12 milk soaps. Sophie creates the order, Thomas prepares and ships it.

D
Sophie — Admin Desktop → Sales & B2B → Orders
Create the B2B order
Sophie selects the reseller "Les Petits Plaisirs", adds the product lines with quantities, and applies the contractual 15% discount. The order is created with status Draft, then confirmed.
Business
M
Thomas — Operator Mobile → Orders → Confirmed tab
See the order appear on his phone
Thomas opens the Orders tab on his mobile. He sees the new "Les Petits Plaisirs" order with the item details, status Preparing, and the requested delivery date. He starts preparing the package.
M
Thomas — Operator Mobile → Orders → detail
Check the details and prepare the delivery note
Thomas taps the order to see the details: reseller, requested date, list of items with quantities, total before tax. He physically packs the box, referring to the list shown on his phone.
D
Sophie — Admin Desktop → Orders → advance status
Advance the status and download the delivery note
Sophie moves the order to Shipped from the desktop. She downloads the delivery note PDF to include with the package. The revenue for "Les Petits Plaisirs" is automatically updated on the reseller record.
The order traveled from Sophie to Thomas without a single spoken exchange. The reseller's monthly revenue is updated automatically, and the delivery history is kept.
⚠️
Business feature Managing B2B reseller orders (creation, status tracking, delivery notes, revenue dashboard) is reserved for the Business plan.

🖥️ Scenario 3.5 — Desktop only

End of month — review and decisions

First of the month. Sophie takes an hour to analyse the past month, identify the most profitable products and prepare for her meeting with her accountant.

D
Sophie — Admin Desktop → Management → Reports
Check the materials consumption report
She filters on the previous month. The report shows total inflows and outflows per material, the total cost consumed, and the most-used material (wax, unsurprisingly). She spots an abnormal consumption of lavender essential oil.
D
Sophie — Admin Desktop → Production → Runs → traceability CSV export
Export lot traceability for a specific run
She locates the run from the 18th that consumed the lavender and downloads the traceability CSV export: lot used, exact quantity, expiry date, supplier. She confirms that a nearly expired lot was indeed used first (correct FIFO).
Pro+
D
Sophie — Admin Desktop → Management → Reports → Financial report
Generate the P&L report by product
She generates the financial report (full-cost method, FIFO valuation). It shows: total revenue, COGS per product, gross margin, allocated fixed costs, monthly break-even point, and a 12-month projection. Fig Candle comes out at 62% gross margin — her best product.
Business
D
Sophie — Admin Desktop → Management → Reports → XLSX accounting export
Download the accounting export for her accountant
She downloads the structured XLSX file: stock movements, FIFO valuation, detailed COGS. She sends it directly to her accountant without having to re-enter a single line.
Pro+
D
Sophie — Admin Desktop → Production → Recipes
Adjust recipes and recommended prices
Armed with this data, Sophie revises the quantities in two recipes and checks the recommended selling price calculated by MakerStocks (COGS + target margin). She decides to slightly raise the price of the Lavender Candle.
Pro+
One hour of analysis replacing half a day of spreadsheet work. All the data is there, structured, ready to be shared with an accountant or used for management decisions.

Key takeaways from these five scenarios

The line between desktop and mobile isn't a line of features — it's a line of timing and role. The admin thinks in terms of the week, costs, and configuration. The operator thinks in terms of the hour, physical action, and confirmation.

MakerStocks is designed so both worlds stay always in sync without ever getting in each other's way: Sophie never has to wonder whether Thomas recorded the receipt correctly. Thomas never has to wonder which runs are the priority. Everyone has the answer wherever they are, on the screen that's in their hand.

📖
Next section Part 4 dives into the functional description of the critical points: exactly how the production cycle works, lot management, and BigCommerce and Shopify synchronization.