Stocksmith
Key Info:
Stocksmith, formerly Craftybase, is cloud inventory, costing and manufacturing software for small-batch product businesses. It tracks raw materials, components and finished goods, connects recipes to production runs, calculates product costs and imports sales-channel activity into one operational inventory record.
Details
Materials and finished goods
Stocksmith distinguishes raw materials, components, work in progress and finished products. Quantities change through purchases, adjustments, manufacturing and imported orders rather than one undifferentiated stock count. A trial should model an actual product with several units of measure and include waste, a substituted ingredient, a returned sale and a supplier price change to verify both quantity and cost behaviour.
Recipes, batches and costing
Recipes or bills of materials describe what a product consumes. Recording a manufacture deducts materials and adds completed products, while batch and lot information can preserve production history. Cost calculations can include materials, labour and overhead. Buyers should compare calculated cost of goods with their accounting method and test nested components, yield variation, rework and a partial batch before using the result for pricing.
Sales channels and purchasing
Connected sales channels can import orders and reduce finished-goods stock, while purchasing records and low-stock information support replenishment. The rebrand from Craftybase to Stocksmith did not create a separate product, so migration and integration records may still show the former name. Verify connector frequency, SKU mapping, duplicate protection, returns and the recovery process when an order import fails.
Fit and evaluation
Stocksmith may suit makers and small manufacturers in cosmetics, food, candles, jewellery and other batch-oriented product businesses. It is more specialised than a generic stock counter but not intended to replace every enterprise ERP or warehouse system. Evaluate locations, traceability, sales channels, accounting exports, tax and COGS treatment, user roles, production reports, imports, support and plan limits with a complete month of representative activity.
Decision record
Record the tested stock model, location structure, exception scenarios, required edition, verified integrations, data ownership, migration assumptions and named operational owner. Define opening-balance approval, cutover reconciliation, user training, support escalation and the measures that will determine whether the rollout is successful. Include a rollback threshold and a dated review of data quality after the first operating cycle. Keep unsupported pricing, customer-size, language and device values blank until a current official source maps them exactly to a BBS field.