Alright, let’s slow this down and troubleshoot it ...

Yep, this absolutely smells like a data-shape / mapping issue, not infra.

Let’s walk it through step-by-step and get you to something you can hand to a dev and fix.

---

1. Confirm what the API is actually returning

For a VIN / listing where you see the flip (N/A → Ask Dealer → blank):

1. Open dev tools → Network tab.
2. Find the Base44 request that populates that page.
3. Copy the full JSON response for that listing.

You’re looking for any of these keys/paths:

• mileage
• miles
• odometer
• specs.odometer
• specs.mileage
• specs.miles
• vehicle_details.mileage

If none of these exist in the payload, then:

• The query isn’t requesting the field correctly, or
• The upstream feed/entity doesn’t store it where you think.

If one of them does exist and has a value, but the UI shows “N/A / Ask Dealer / blank”, then the bug is 100% in your mapping/frontend logic.

---

2. Fix the Base44 query

Whichever backend layer is calling Base44 (GraphQL, REST, whatever) needs to explicitly request the mileage/specs fields.

Example (pseudo-GraphQL style):

graphql
vehicle(id: "…") {
  id
  vin
  price
  # Make sure these are included:
  mileage
  miles
  odometer
  specs {
    mileage
    miles
    odometer
  }
  vehicle_details {
    mileage
  }
}

Then re-test that the response actually contains those fields for a known listing.

---

3. Normalize the mileage on the backend (recommended)

Instead of your frontend guessing which field to use, normalize it once in your API layer.

Pseudo-TS/JS:

ts
function normalizeMileage(raw: any): number | null {
  const candidates = [
    raw.mileage,
    raw.miles,
    raw.odometer,
    raw.specs?.odometer,
    raw.specs?.mileage,
    raw.specs?.miles,
    raw.vehicle_details?.mileage,
  ];

  const value = candidates.find(v => v !== undefined && v !== null && v !== '');
  const numeric = typeof value === 'string' ? parseInt(value.replace(/[^\d]/g, ''), 10) : value;

  return Number.isFinite(numeric) ? numeric : null;
}

Then return something like:

json
{
  "mileage": 43210
}

…so the frontend doesn’t care where it originally came from.

---

4. Clean up the frontend fallback logic

Your current behavior:

• When not mapped → "N/A"
• After some other logic or partial mapping → "Ask Dealer"
• After more changes → "" (blank)

That usually means you have multiple conditional passes acting on the same field (maybe different components or hooks). You want a single, simple rule:

ts
const mileage = listing.mileage; // already normalized by backend

const mileageLabel =
  mileage == null
    ? 'Ask Dealer' // or 'N/A', pick ONE
    : `${mileage.toLocaleString()} miles`;

No multiple fallbacks, no flipping state.

---

5. Concrete debugging checklist

You can literally hand this to the dev:

1. Capture payload for a problem vehicle and confirm where (if at all) mileage is stored.
2. Update Base44 query to request:
   • mileage, miles, odometer
   • specs.mileage, specs.miles, specs.odometer
   • vehicle_details.mileage
3. Add a normalization function server-side that outputs a single mileage field.
4. Update UI to only read normalizedMileage and use a single fallback rule.
5. Regression check on:
   • A vehicle with known mileage
   • A vehicle truly missing mileage
   • A few different dealer feeds

If you paste one full sample JSON response for a “broken” listing, I can show you exactly how I’d map it and what your normalized object should look like.