Pet Waste Removal Software — Data Model | FieldCamp

How a pet waste removal business runs in FieldCamp — recurring routes, residential subscriptions, commercial HOA accounts, and waste stations on one model.

A pet waste removal business runs almost entirely on FieldCamp's core records. Weekly and biweekly scoop routes, crews, online sign-up, recurring billing, and on-site arrival and completion photos are all there the moment you sign up.

The chain a pooper-scooper operator already lives by — a homeowner signs up for a plan, you put them on a repeating route, a tech scoops the yard and texts a photo of the secured gate, and the card on file gets billed every month — is modeled directly as Customer → Job → Visit → Invoice → Payment.

Most of this needs no setup. A few small touches — number of dogs, the gate code, the plan tier, and waste stations for commercial sites — are added as custom fields and one custom object.

What the core already gives you

Most of a pet waste removal business is covered by records that work on day one, with no setup.

Recurring scoop routes. A Job set to recurring auto-generates its Visits from a weekly, biweekly, twice-weekly, or monthly pattern, so a route schedules itself.
Crews on every stop. Each Visit is staffed by one or more team members, matched by skill and service area.
Route density and territory. Service Areas cluster stops by zip code and zone, and the dispatcher orders the day so a tech covers a dense route efficiently.
Subscriptions and recurring billing. A recurring Job plus a Service Agreement carries the plan term and cadence; Invoices bill the card on file monthly and track paid, partial, and overdue.
Online sign-up and quotes. A Request captures an inbound sign-up or quote and converts into a Job or Invoice in one step.
Arrival and completion proof. Visits track en route, arrived, and done with check-in and check-out location, and a completion photo — the secured-gate shot customers expect.
A priced catalog. The price book holds weekly, biweekly, one-time, and deodorizing services priced by the unit, with cost and price separated.

The Customer record already separates service, billing, and property addresses, and marks each account as an individual or a business — enough to tell a residential home from a commercial site.

There is no separate "subscription" record to build. A pet waste removal plan is a recurring Job for the cadence plus a Service Agreement for the term, renewal, and cancellation — both already in the model.

Tailoring it to pet waste removal

Most of what this trade needs that core does not already name is a handful of fields, not new records.

Pricing keys off the number of dogs, the yard size, and the frequency; the tech needs the gate code to get in; and the account sits on a plan tier.

These ride directly on the core records as custom fields — no new object required.

Field	On record	Field type	What it holds
Number of dogs	Customer	Number	How many dogs, a driver of price and scoop time
Yard size	Customer	Single choice	Small, medium, large, or extra large
Gate code / access	Customer	Text	The gate code or lockbox value the tech needs
Access notes	Customer	Long text	Locked gate, pet warnings, where to leave bagged waste
Plan tier	Customer	Single choice	Weekly, biweekly, twice-weekly, or one-time
Areas to service	Job or Visit	Long text	Which parts of the yard to cover
Gate secured photo	Visit	File	The proof-of-secured-gate shot on completion

The gate code is the field a route tech reaches for first. Put it on the Customer so it shows on every Visit the route generates, rather than re-typing it on each stop.

The recurring-vs-secured-gate detail is also a Job Form: a short per-visit checklist — yard scooped, waste bagged and stowed, gate latched, photo taken — captured on site and stored on the Visit, with the photo requirement turned on for the completion step.

The one object commercial adds: a waste station

Residential accounts need none of the above as a new record — the fields cover them. Commercial work is where a real object earns its place.

HOAs, apartment complexes, and dog parks pay you to install, service, restock, and maintain pet waste stations — the post-mounted bag dispensers and trash cans around a property.

A station is a long-lived physical asset with its own location and service history, serviced on every visit.

That is a thing the business tracks in its own right, so it is a custom object, modeled the same way as Equipment or a pest-control bait station.

A Station belongs to a Customer's property and is serviced on each Visit the recurring route generates.

Field	Field type	What it holds
Station number	Text	The label or tag on the station, used to find it on site
Location / zone	Text	Where the station sits — "north gate," "dog park entrance"
Station type	Single choice	Single-post dispenser, dispenser with bin, or bin only
Install date	Date	When the station was placed
Bag type	Link	Linked to the price book bag product it dispenses
Last serviced	Date	The most recent service date
Condition	Single choice	Ok, needs restock, damaged, or missing
Notes	Long text	Free-form notes on the station and its placement

A Station page is assembled from building blocks: a header with the condition pill, a breadcrumb back to the property, the station fields, the address with a map pin, a related table and service history of its servicing, a photo gallery, and a timeline.

A Customer holds the recurring Job, the plan, and the Stations installed at the property.

Each Job is scheduled as Visits, and each Visit services and restocks the Stations on the site — so every station builds a dated service history instead of one overwritten status.

A Station carries a short lifecycle of its own.

It starts active, flags as needs-restock or damaged when a visit finds it that way, returns to active once serviced, and ends as removed — with the return step able to require a service photo on commercial sites.

Residential accounts skip the Station object entirely. A home has no dispensers to maintain, so the number-of-dogs, yard-size, and gate-code fields on the Customer are all the tailoring it needs.

Residential subscriptions vs commercial accounts

The same backbone serves both sides. What differs is which pieces carry the weight, and how completion is gated.

Residential subscriptions

One customer to one yard. The recurring Job is the subscription, the plan tier and number-of-dogs fields drive price, and the gate code gets the tech in. The Service Agreement is light — often just the cadence and an easy cancel-anytime term. Completion is a quick scoop, a bagged-waste note, and a secured-gate photo. Dense same-day routes are ordered by Service Areas and the dispatcher.

Commercial accounts

HOAs, apartments, and dog parks. One account holds many Stations across the property, so the Station object is essential — a property manager may have dozens of dispensers under one account. The agreement carries site terms, a longer duration, and renewal. Completion is heavier: each station serviced, restocked, and logged, with a photo required as proof.

You build the fields and the Station object once. Residential accounts lean on the recurring Job and the Customer fields; commercial accounts add the Stations and the heavier completion.

The completion difference does not need a second workflow. The same Visit workflow can require a photo for commercial sites and leave it optional for residential — one pipeline, configured per account.

Built on the customization engine

Everything here is built with the same tools every FieldCamp account has.

The pet-waste fields are custom fields on the core records; the waste Station is a custom object with its own fields and a short active-to-removed lifecycle; and each record page is arranged from a library of building blocks.

Add a field, rename a stage, or arrange a page to match how your routes actually run, using custom objects and fields, stages and workflows, and record layouts.

Built for any size. A one-truck operator runs a dense residential route on the core records plus a few Customer fields. A multi-location franchise servicing HOAs and apartments adds the waste Station layer — on the same backbone, no rebuild.

Coming from Sweep&Go

Most scoop businesses on Sweep&Go can bring their structure into FieldCamp directly — the clients, the recurring plans, the yards with their dog counts and gate codes, the routes, the visits, the crews, and the commercial stations all have a home here.

The difference is that in FieldCamp you own and shape the model, rather than fitting your business to a fixed one.

In Sweep&Go	In FieldCamp	Notes
Client	Customers	The dog owner or property manager. FieldCamp keeps service, billing, and property addresses on one record, and marks each account as individual or business.
Subscription / recurring plan	Service Agreements	The plan term, cadence, and cancellation behind a weekly or biweekly scoop, paired with a recurring Job for the schedule.
Property / yard info	Customer fields — number of dogs, yard size, gate code	Captured as custom fields on the account, so they show on every visit the route generates.
Route	Service Areas	Stops clustered by zip and zone, with the dispatcher ordering a dense day.
Job	Jobs	The recurring scoop route — one-off, multi-day, or recurring.
Visit / completed job	Visits	Each scheduled stop, with dispatch, en-route, on-site, check-in, and the secured-gate photo.
Online sign-up	Requests	An inbound sign-up or quote that converts into a Job or Invoice in one step.
Staff / crew	Team Members	Assigned to visits, matched by skill and service area.
Invoice / auto-pay	Estimates & Invoices	Monthly billing against the card on file, with paid, partial, and overdue tracking.
Pet waste station	A custom Station object (custom objects)	The post-mounted dispensers on a commercial site, tracked as assets with service history.
Dog info	A Customer number field	The dog count that drives price and scoop time.
Cross-sell / one-time service	A line item from the Price Book	Deodorizing, haul-away, and add-ons priced by the unit.

What you gain. In Sweep&Go the structure is fixed — the records, their fields, and how they relate are set for you.

In FieldCamp every one of those records is yours to rename, extend, restage, and relayout, so you can match your old setup first and then go past it with custom objects and fields and your own automations.

One honest difference. Sweep&Go ships a built-in subscription engine with auto-pay billing and a branded sign-up portal that runs the recurring charge on its own schedule.

FieldCamp models the plan itself as a Service Agreement that carries the cadence, renewal, and price and schedules the next scoop Job; the recurring billing runs through the standard invoice flow rather than a separate billing engine.

If automatic charge cycles and a turnkey sign-up page are central to how you run, plan that part of the move deliberately.