How Developers Share Property Inventory With Specific Brokers

Developers can distribute inventory selectively by defining two things independently: which units belong to a release and which brokerages may access it. Project discovery, commercial visibility and transaction permissions should not be collapsed into one public/private switch.

This matters when a master broker receives an early allocation, a specialist agency gets a particular unit mix, or a developer opens the remaining inventory to a wider network. A forwarded spreadsheet cannot reliably preserve those boundaries.

#Start with the commercial decision

Write a short release brief before selecting anything in software. Identify the project, purpose, eligible units, audience, timing, sales contact, permitted materials and applicable commercial terms.

For example, a developer has 120 units but wants an initial release of 20 one-bedroom apartments to three named agencies. That instruction has at least four independent dimensions:

The remaining 100 units do not become part of the release merely because they share a project name. Likewise, sharing with one agency must not expose a different agency's negotiated terms.

#How the Nogbase release workflow is organized

Nogbase's release builder includes project selection, unit selection and a brokerage audience. The audience choices distinguish Selected brokerages from All active brokerages, and the preview displays resolved units and the selected audience.

An authorized developer user should:

1. Open the project's release or listing workflow and select the correct project.
2. Choose the intended units or selection criteria, then inspect the resolved unit set.
3. Select the brokerage audience. Use named agencies for a controlled allocation.
4. Review project and commission readiness, plus the approved materials.
5. Preview the release and verify the unit count and audience before publishing.
6. Test the result from an authorized broker account and an account outside the audience.

Menu locations can change between releases. The important control is the preview of the actual audience and resolved inventory, not the label of a button. Use the Developer App preview to check the release before publishing.

#Separate a directory profile from operational access

A broker may discover a project through a developer directory or catalog while still needing access to its live inventory and transaction workflow. Public project facts are not a promise that every unit is offered for sale through that broker.

Treat these as separate questions:

• Can the agency discover the project?
• Can it view the selected unit's current commercial details?
• Can it download this particular file?
• Can it submit an EOI?
• Who can approve a hold or reservation?

This distinction also prevents marketing teams from interpreting catalog totals as immediately reservable stock. EOIs and reservations have different meanings and should have different permissions.

#Keep commission terms private to their audience

A public headline commission and a negotiated agency agreement are not the same record. If Agency A receives a special arrangement, do not place its agreement in a brochure or shared folder accessible to Agencies B and C.

Before publishing, check the commission basis, beneficiary, effective dates and whether a temporary incentive replaces or supplements the normal policy. Keep the commission calculation and release rules tied to the agreed scope. Access to inventory should not silently grant permission to edit financial terms.

#Test availability when two brokers want the same unit

Sharing inventory does not eliminate concurrency. Two brokers may inspect the same available unit before either request is accepted. The server must recheck availability when the action occurs, enforce the relevant hold or reservation rule, and explain when the unit is no longer available.

Use a deliberate test during onboarding: have two authorized users attempt the same controlled action, then verify the resulting status and audit trail. Do not rely on a screenshot that happened to display “Available.” A visual update and an authoritative reservation are different things.

For temporary holds, confirm who owns the hold, when it expires and what happens on release. An EOI acknowledgement should never be mistaken for a guaranteed allocation.

#Review access after the launch

The release audience will change. An agency may leave the network, an agreement may expire or a specific allocation may be withdrawn. Assign an owner to review those events and verify that the resulting permissions match the new commercial instruction.

Revocation prevents future access; it cannot erase a downloaded PDF or screenshot. Limit the information shared initially and keep pricing or availability in a controlled current view whenever possible. Existing deals may need continued access to their historical terms even when new inventory access is removed; handle that distinction deliberately.

#A pre-release acceptance checklist

• The intended units match the preview, including exclusions.
• The audience consists of the intended broker agencies.
• An outside agency cannot retrieve restricted inventory or materials.
• Each agency sees only its applicable private terms.
• Sales contacts and brochure revisions are current.
• EOI submission and developer approval are distinct actions.
• Holds, expiry and competing requests behave as expected.
• Access changes leave an understandable activity record.

Selective distribution works best when the broker experience is still simple: one place to find the approved material, see current availability and take the permitted next step. Pair these controls with a developer promotional toolkit and a clear launch preparation process.