Own catalogue: sales map, demand model and market advisor (plan)

New docs/catalogue-intelligence.md for Alexander's idea of a catalogue
the plant presses for itself. Why (idle Classic hours ~60k to 160k
records a year at 60 % specials on the doc basis; two-week represses
from the metal archive; Thai catalogue sells in Japan, EM Records,
ZudRangMa), scope (Poy Records as seed; customers' data and press dates
protected), data sources with access terms (Bandcamp ship-to fields,
distributor sell-through clauses, opt-in record passport registrations,
Spotify for Artists, Discogs CC0 dumps; Discogs API marketplace and
want data restricted), ERPNext touchpoints (Licence, Channel Sales
Report, Catalogue Recommendation, geocoded addresses, CRM), PDPA rules
for the map, dashboard views on an open-source map stack, a staged
demand model with a stocking rule for run size, a propose-only advisor
on an open-weights model, phasing, cost estimates, risks and open
decisions.

Backlinks: README (planning documents, layout), roadmap item 28,
digital-factory tool rule, artist-platform repress pre-orders,
production-timeline repress, revenue-model ResurRec Japan.
This commit is contained in:
grabowski committed 2026-10-27 09:28:51 +07:00
1 parent 793ea02c22
commit d36a6fdd02
7 files changed
+446 -4

No files matched your search

+3 -1
View File
@@ -451,7 +451,9 @@ without a new cut) and a repress takes
([production timeline](production-timeline.md)). The campaign page can
reopen as "pre-order the repress, pressed when 100 more are in", which
turns one release into a recurring one. This is the part a plant with
in-house plating can offer and a broker cannot.
in-house plating can offer and a broker cannot. The same pre-order is
the market test for titles of our own
([own catalogue](catalogue-intelligence.md)).
## For labels and regular customers