Property and residential

Available now

Yardi RentCafe Integration for Resident Parcel Tracking

Pull residents and unit/bed from the Yardi RentCafe API.

  • Read-only
  • Scheduled sync
  • No new hardware

Yardi already holds the resident and the unit. The parcel room needs exactly those two facts and usually gets them second hand.

What follows is familiar to anyone who has run a concierge desk. Somebody keeps a list. The list is right in January and drifting by March. New residents get added when someone remembers; leavers get removed when a parcel turns up for them and prompts the question.

The cost is not really the admin. It is that staff stop trusting the list, and once that happens they start holding items, asking colleagues and calling residents to check. A parcel room where nobody trusts the recipient list is slow in a way that no amount of process improvement fixes.

Reading residents and their unit or bed from the RentCafe API removes the human step. The desk sees the same occupancy the property team does, refreshed on a schedule.

The real gain is trust. Staff work quickly when they believe the list, and a synced list is the only kind they believe.

What comes across

For residential and student operators running Yardi with the RentCafe API available.

  • Residents

    Current residents as Yardi holds them, so the desk is not maintaining a parallel list that slowly goes wrong.

  • Unit and bed

    The location, down to bed level where you use it, so notifications tell people exactly where their item is.

  • Turnover handled

    Arrivals and departures come through automatically, which is what keeps the list worth trusting.

Where the data lands

Two Traizr screens: the recipient directory the connector keeps current, and the parcels matched against it.

The Traizr recipient directory, listing recipients with their email address and room or suite
Recipient directory in Traizr. Yardi RentCafe keeps this list in step with your source system, so nobody adds and removes people by hand.
The Traizr parcels screen, showing items matched to named recipients with courier, location and status
Parcels matched to those recipients, with courier, location and status. This is what the synced list is for.

How the integration works

Set up once, then it runs without anyone thinking about it.

  1. Connect it

    You give Traizr read access to Yardi RentCafe API. Traizr only ever reads from your system; it does not write back into it.

  2. Map the fields

    Decide which field is the recipient name, which is the email, and which carries the room, unit or department. Done once, at setup.

  3. Set the schedule

    The sync runs on a schedule so the recipient list keeps itself current. Nobody has to remember to export anything.

  4. Parcels start matching

    From then on, an item scanned at the door is matched against a live recipient list, and the notification goes to the right person at the right location.

Questions people ask

What access does Traizr need?

Read access to the Yardi RentCafe API for the properties you want covered. The connector is read-only and never writes back into Yardi.

Does it work for student accommodation as well as multifamily?

Yes. Bed-level location is supported, which is what student sites usually need. Student accommodation parcel management covers that setup.

Can we cover several properties?

Yes, under one account, each with its own recipients, notifications and reporting.

How quickly does a new resident become a valid recipient?

On the next sync after they appear in Yardi. Sites with high turnover run the sync more often for exactly this reason.

What if some buildings are not in Yardi?

They can run alongside, either maintained directly or fed from the CSV connector. A mixed estate is a normal setup.

Want this connected to your Yardi RentCafe?

Tell us what you run and we will walk through the setup on your own data. About 20 minutes.