Fotona systems — including SP Dynamis, XS Dynamis, and StarWalker configurations — look similar across generations, but the hardware and software differences between them decide what a used unit can actually do in your clinic. Two consoles with the same brand name can be different platforms, and two identical models can be worth very different amounts depending on the handpiece set, software version, ASP-related features, and service history.

This guide gives you a Fotona-family verification path: identify the exact model first, then verify handpieces, software and ASP claims, visible condition, and records. It is written for buyers who need to confirm what they are paying for before the deposit leaves the account — not for service engineers, who will take these checks further with test equipment.

Identify the exact model, generation, and year first

Start from the console, not the listing title. Fotona has marketed several SP and StarWalker generations, and model naming differs between markets and years. The family names buyers meet most often on the secondary market are these:

Ask the seller for a legible photo of the console nameplate showing model and serial, the year of manufacture, the original invoice or import document if available, and the software version shown on screen during a live video call. Then ask the seller to state, in their own words, which generation and configuration this is — and what console evidence supports that statement.

If the seller cannot or will not produce a nameplate photo, treat the listing as unverified regardless of the photos in the ad.

Model-family checkpoint notes

Each family has checkpoints that deserve extra attention on the used market:

• SP Dynamis family: confirm the generation and the Er:YAG/Nd:YAG handpiece pairing in the quote; sellers sometimes describe an older console with newer marketing language.
• XS Dynamis family: verify the compact console’s included handpieces against your planned menu — small-footprint systems are still platform-specific, and a missing head changes capability.
• StarWalker family: confirm the exact model and generation (MaQX/PQX-era naming), the software version, and any ASP or pulse-format status, because those features vary by generation.

If the seller cannot name which family the unit belongs to from console evidence, the listing is not yet ready for price comparison — identification comes first.

Handpiece inventory and part-number verification

Fotona systems run on model-specific handpieces, and the handpiece set is a major value driver on the used market. Handpieces such as the PS03/PS03X family, R-series heads, and scanner and specialty heads appear in whole-system quotes and in separate parts listings, so the same specificity is needed in both cases. For every handpiece in a system quote:

• Request close-up photos of the part number and any serial markings printed on the handpiece or cable.
• Confirm compatibility with the exact console model and generation — “fits Fotona” is not compatibility evidence.
• Check the optical window, cable, and connector condition, and photograph the connector end.
• Count the set against the quotation line by line, and ask which handpieces are optional versus included.

Handpiece scarcity is a real cost driver: a console priced low because it ships without the handpiece your protocols need is not a bargain once replacement cost is added.

ASP, software, and calibration evidence

Fotona markets ASP pulse-shaping technology on some StarWalker configurations, and software/self-calibration state affects both function and service. Claims about ASP or calibration belong in records with numbers and dates, not in the listing description. Ask for:

• The software version and any ASP, pulse-format, or self-calibration status shown on screen during the live walkthrough.
• A dated service record naming the console serial and listing what was tested or calibrated, with readings where available.
• Confirmation that software updates are available through an authorized path in your region and whether service eligibility transfers.

If the seller describes the unit as “ASP-enabled” but cannot show the setting in the software or name the model generation that includes it, ask for manufacturer documentation rather than accepting the claim.

Visible checks that do not require opening the console

These buyer-observable checks confirm the unit is physically complete and well cared for; they do not certify output:

• Cabinet and casters: impact damage, corrosion, or storage in poor conditions.
• Ventilation: fan and vent condition that hints at service intervals.
• Connectors and ports: bent pins, cracked housings, or aftermarket repairs.
• Foot switch and accessory connectors present and intact.
• Labels: nameplate and regulatory labels legible and present, with no signs of tampering.

Photograph each of these areas during the pre-payment walkthrough so arrival condition can be compared honestly.

Records and acceptance terms

Function evidence has a hierarchy, and you should collect it in this order:

1. A dated service record with measured values, naming the console serial.
2. Screen-level serial, software, and error-log evidence from a live call.
3. Original ownership paperwork or a written chain-of-custody trail.
4. Registration or import paperwork that applies in your market.

Then agree acceptance terms in writing: which checks happen before payment, which happen after arrival, who performs the functional test and pays for it, and what happens if the unit fails or the handpiece set arrives short. Photograph the crate before signing the delivery receipt — freight damage is common, and the receipt signature decides who owns the argument.

Attach the acceptance terms to the deposit request, not after it. A short paragraph in the purchase agreement — “console serial matches quote; handpiece inventory verified line by line before payment; functional test scheduled within seven days of arrival; seller responsible for freight damage documented at receipt” — converts the whole guide into a contract, which is where verification actually gets enforced.

If the seller offers a “dealer certification,” ask what it covers in the same language you would use for any other claim: which tests were performed, by whom, on which date, and what the certification excludes. A certification that documents a boot test is not a certification of output; a certification that lists measured values is a different document. Read the words, not the seal.

Building the evidence file

Organize everything into one file per unit: nameplate photo, live walkthrough recording, line-item handpiece inventory with photos, service record, ownership chain, and acceptance terms. A clean evidence file is also a negotiation asset — sellers who know their unit is verifiable are usually willing to let it be verified.

Compare evidence files before you compare prices. Fotona inventory with documented serial and handpiece details can anchor the first file; hold every other listing to the same standard. The unit whose paperwork matches its console is the one worth your deposit.