What Campbell Hotel Guide Actually Does
Campbell Hotel Guide is a property management and guest communication tool designed for boutique hotels and smaller chains. It handles reservation tracking, housekeeping assignment, guest messaging, and billing in one interface. You sign up through their portal at campbellhotelsolutions.com and it takes about twenty minutes to get the basic setup running. The interface looks like it was built in 2018 and hasn't had a major redesign since. That's not a problem if you just want it to work. Download the installer from their site and run it on a Windows machine. It won't play nice on macOS without a virtual machine, which is worth knowing before you spend an hour trying to figure out why it won't launch. During installation you'll need your property's tax ID and a valid credit card. They charge $49 per month per property, though the first thirty days are free. Skip the optional add-ons during setup. The upsells for online booking integration and loyalty programs are overpriced and mostly redundant if you already have a channel manager. After installation, go into Settings and map out your rooms. Input each room with its type, floor, and maximum occupancy. Then configure your rate plans. Here's where most people mess up: don't stack more than three rate plans per room type. The system starts dropping rate updates at certain times when you have five or six competing plans active. I learned this the hard way when I had eight different promotional rates running during a renovation period, and two of them showed zero availability even though the hotel was empty. Turned out the engine couldn't reconcile the overlaps. Cut it back to three and everything synchronized within an hour.
Connect your payment gateway. Stripe and Square both work. PayPal is technically supported but I've seen at least three properties experience failed transactions that cleared in the host system but never hit the bank. Disable PayPal unless you specifically need it. The PCI compliance module alone will cost you another $15 a month, which is unnecessary if you're just using Stripe.
Daily Operations Workflow
Once configured, your morning routine should take about fifteen minutes. Log in, check the arrival list, assign housekeeping orders, and confirm any special requests. The housekeeping board defaults to alphabetical order by room number, which seems fine until you're dealing with a property where the hallway doesn't match the room numbering. I worked with a client who had rooms 301 through 315 but the actual wing layout put 307 right next to 302 around a corner. Their maids were walking back and forth across the entire floor unnecessarily. Redid the floor plan in the system to match the physical layout instead of the numerical order, and it cut their cleaning rotation time by roughly forty percent. The check-in process itself is straightforward. Pull up the guest record, verify ID, run the card authorization, and mark the room as occupied. Print the registration card if your state requires it. Don't skip that step. I've seen two properties get audited because they thought digital signatures were enough, and the licensing board didn't agree.
Get the Full Details
Common Problems and Workarounds
Here are the issues I've actually encountered, not the ones from their FAQ page. Sync failures with external booking platforms. If you use Booking.com or Airbnb alongside Campbell Hotel Guide, expect sync gaps. The API connections are real-time but they stall during high-traffic periods, usually between 2 PM and 6 PM local time. I solved this by setting a manual refresh interval at 12-minute increments during those hours instead of relying on automatic sync. It's tedious at first but prevents the double-booking nightmare that happens when the system misses a cancellation. Housekeeping status updates getting lost. About once a week, a room will show as "dirty" in the system when the maid has already completed it. This isn't a bug, it's a timeout issue with the tablet app on their iPad Minis. The tablets disconnect from the server every few hours. My workaround was to set up acron job that forces a reconnection every two hours during the cleaning shift, and I also printed a physical checklist as backup for the mornings the tablets are offline.
Billing calculation errors on extended stays. If a guest books more than fourteen nights, the system sometimes miscalculates the weekly discount tier. I caught this when a repeat guest's monthly rate came out $200 higher than it should have. The fix is to manually override the discount after the fourteenth night, then note the adjustment in the guest ledger. Flagging it prevents audit issues down the line.
What Campbell Hotel Guide Can't Do
It won't integrate with major POS systems beyond basic receipt export. If you need restaurant charges flowing directly to the folio, you'll need a separate middleware solution, which adds another $29 monthly. It also has no native support for group blocks of more than twenty rooms. You can create them manually but the rooming list feature breaks down past that threshold and you end up managing spreadsheets outside the system anyway. For that scenario, I'd recommend looking at Cloudbeds or Oracle Hospitality instead. The switch-over is painful but it's faster than wrestling with Campbell's workarounds for large events. Campbell Hotel Guide works well for properties with under fifty rooms and a small front desk team. If you're running a twenty-room bed and breakfast with one person doing everything, this is probably the simplest option available at this price point. It won't scale past that comfortably. The reporting engine is adequate for basic P&L statements but if you need revenue management analytics or dynamic pricing suggestions, you'll need to supplement it with something like Duetto or RateTiger. That said, adding those tools is possible through their API, though the documentation is sparse and the sandbox environment is slow. The update cadence is another factor. They push patches every six to eight weeks, and each update carries a small risk of breaking an existing integration. Always test on a demo property before applying updates to your live system. I keep a clone of my production database and run every update there first. It adds about forty-five minutes to each patch cycle but has saved me from three separate outages over two years.
