The Series· No. 13 · Act III — The Catalog

By DocuSeller · Published

Pricing
DocuSeller · No. 13

Four hundred prices, one click

Ever noticed a checkout that asks for your address sometimes and not others?

It isn't a bug. Something in the catalog knows whether anything has to physically move.

Three handling tiers offer configured turnaround times and fees Handling optionsTiming and fees are configuredStandardStandard turnaroundRushFaster turnaroundExpressShortest turnaround
Same documents. Three different promises about when.

Every package can carry two sets of tiers. Think of the board above a counter: the item, then the options listed underneath it.

Handling time: Standard, Rush, Express. Each tier carries its own fee and its own promise, measured in business days rather than vague optimism.

Delivery: Electronic, Standard, Expedited.

Electronic delivery needs no shipping address, while physical delivery does ElectronicPhysicalNo addressAddress needed
Only one of these needs an address. The catalog already knew that.

And the physical tiers carry a flag that says: this one needs somewhere to go.

That flag is why checkout behaves differently. Nothing to ship, nothing to ask.

Now the part that saves a company its worst week of the year.

Options resolve on three levels. Association, then company, then platform. Most specific wins.

Association overrides take precedence over company settings and platform defaults Use the most specific configured option1AssociationUse its override2CompanyOtherwise use company settings3PlatformOtherwise use platform defaults
Most specific wins. Set it once at the base, argue only at the top.

So you set the house price list once at the base and override only where a community genuinely differs. Which, across fifty states with fifty sets of fee caps and deadlines, it genuinely sometimes does.

Same idea with the packages themselves.

A company-level package can be shared out to every association it manages. Off by default, because nobody wants a new product materialising on their storefront overnight.

Each community either sells it as-is or clones it into a copy they can edit. And a shared package renders against the buyer's community, so one recipe still produces the right local documents.

Then, once a year, the bit everyone dreads.

Raise prices by 6%. Or by $25. Or set a flat number. Across the ten products you ticked, or across everything matching the filter you're looking at. With a live before-and-after, so you see the new numbers while you can still change your mind.

An example six-percent price adjustment previews current and new prices before confirmation Preview the change before applying itExample: +6%ProductCurrentPreviewResale package$400$424Disclosure bundle$550$583Review the affected products, then confirm
Four hundred prices. One preview, then one click, then lunch.

Nobody has ever hand-edited four hundred prices and been in a good mood on Monday.

Standardise centrally. Deviate locally. Never edit four hundred things by hand.

And quietly, rush and delivery are the most dependable upsell on the whole order.

Next: what happens in the seconds after someone clicks Pay, when the package stops being a list and starts being a job.

#PropTech · #HOA · #SaaS