Domain for a Singapore-based warehouse search around New York

[daan_finch]

I’m based in Singapore and used Domain while looking for a warehouse around New York. Coverage was useful, but duplicates, stale status and inconsistent floor-area entries made side-by-side comparisons harder than expected.

Oddly, school catchment information was the feature I valued most because the wider location also mattered to me. The main gaps were a clear “last verified” date and an obvious next step after finding a listing. I’m deciding whether to keep Domain as my main search tool or use it only for discovery. How do others assess freshness, particularly on mobile and after contacting an advertiser?

 

[jade_saves]

Based on those issues, I’d treat it as discovery rather than the main record. Keep a separate shortlist with the address, advertised area, status, contact date and any duplicate links. If two entries disagree, don’t assume the newer-looking page is correct; ask the advertiser to confirm both availability and the relevant floor-area definition.

 

[solid_canvas]

Were you looking to buy or lease? That changes what the useful next step should be. Also, were the floor-area conflicts between duplicate advertisements for the same warehouse, or simply different fields within one listing? The first suggests poor duplicate control; the second may be a measurement-label problem.

 

[GoodSignal]

A fresh date helps, but it can also mislead if it only records a minor edit. I would keep a warehouse on the shortlist only when the status is clear and the advertiser confirms that it is available, along with which floor-area measurement applies. The timestamp is supporting evidence, not verification on its own. Saved-search alerts are useful for spotting changes, but I would still record the advertiser’s response and confirmation date separately.

 

[kai_cole]

Map-pin accuracy deserves equal attention for a warehouse search. Even a small placement error can make the surrounding roads and access points look different on mobile. Before contacting anyone, compare the written address with the pin and note discrepancies in your shortlist. That also helps identify duplicates using slightly different location descriptions.

 

[kai_cole]

One addition to that: save screenshots or notes when you first shortlist something. If the status, area or price later changes, you can ask a precise question instead of relying on memory. A price-history field or linked sold record would help with context, but neither would resolve whether the current advertisement is still live.

 

[swimsAndSignal]

Mobile filters are where I’d decide whether the portal remains useful day to day. Can you retain warehouse-specific criteria after reopening the app or browser, and do saved-search alerts preserve those filters? An alert that drops an area or property-type filter may create more duplicate checking than it saves.

 

[SimpleWall]

The school-catchment point is interesting for a warehouse. Was it helping you understand nearby residential areas, or is this a mixed personal and business property decision? If it’s purely a warehouse search, I’d be cautious about letting a well-presented secondary feature outweigh weak status and floor-area data.

 

[testTheLane]

The missing transaction step may partly reflect an expectation mismatch. A listing portal can introduce the property and advertiser, but the process after contact varies by property and jurisdiction. Since you’re in Singapore and searching around New York, write down what you need before contacting anyone: confirmation of availability, exact area basis, price terms, address and who handles the next stage.

 

[jae.finch]

Duplicates can still be informative if you compare them rather than immediately deleting all but one. Different photos, area figures or status descriptions reveal what needs clarification. I’d group records by address, mark the conflicting fields, and send one consolidated set of questions. That is less frustrating than contacting every version separately.

 

[hana.slate]

I wouldn’t expect sold-record links or price history to solve the comparison problem on their own. Warehouses can differ materially even when nearby, and an unexplained historical number may invite a misleading comparison. Accurate current fields and a clear update trail would be more valuable first; historical context comes after that.

 

[kai_cole]

A practical test would be to keep five listings and track them for a week or two. Record when each first appeared to you, whether an alert repeats it, whether the mobile pin matches the address, and what happens after contact. That small sample should reveal whether the problems are occasional or systematic enough to justify switching your main workflow.

 

[SimpleWall]

That test also answers my earlier concern about the catchment feature. If the core warehouse details remain unreliable across the sample, a useful neighbourhood layer shouldn’t keep the portal in the lead. If most listings verify cleanly and only duplicates need manual grouping, it may still work well as the discovery layer Oscar suggested.