PlatformFeaturesPricingHelpVerify Passport
NEXPURA
AboutBook a DemoLoginStart Free Trial
PlatformFeaturesPricingHelpVerify PassportAboutBook a DemoLogin
Start Free Trial
NEXPURA

The operating system for modern jewellers.

Product

  • Platform
  • Features
  • Pricing
  • Security

Resources

  • Blog
  • The Problem
  • Help

Company

  • About
  • Contact
  • Book a Guided Demo
  • Start Free Trial

For Customers

  • Verify Passport

Legal

  • Terms
  • Privacy

© 2026 Nexpura. All rights reserved.

Built for jewellers.

Back to all docs
Documentation · Section 3

Memo & Consignment

Memo and consignment-in goods are pieces sitting in your case that you don't own yet. Nexpura models them as a distinct inventory state with their own return-window dates and supplier references, so they never get confused with the stock you bought outright. Three pages: the data model, the receiving workflow at /memo/new, and how a memo piece exits — either returned to the supplier by its window date or bought to convert it into owned inventory.

01

Memo & consignment overview

The data model — memo-in, memo-out, and consignment — why memo is a first-class inventory state distinct from owned stock, and how return windows, supplier references, and status transitions hold together.

02

Receiving a piece on memo

The intake workflow at /memo/new — capturing the supplier, the agreed value and commission, the return-window date, and posting the piece into the Consignment In tab without it landing in owned-inventory valuation.

03

Returning a memo piece — or buying it

The two ways a memo piece exits the Active state. Return by the window date posts a clean return-of-goods movement. Buying the piece converts it to owned inventory — that conversion path is being built; the manual workaround is documented inline.