@fluid-app/fluid-cli-localization

Fluid CLI plugin for selling in another country and in another language. It adds two command groups:

• fluid countries opens a country from Fluid's Country Atlas, converts your prices into its currency, creates its agreements, and checks the result.
• fluid translations turns languages on, reports what shoppers would still see untranslated, machine-translates it with Fluid AI, and writes it back.

The country flow hands language work to fluid translations, so each step has one command.

npm install -g @fluid-app/fluid-cli @fluid-app/fluid-cli-localization
fluid login

# Open a country
fluid countries atlas DE                       # the atlas: modes, tax, legal, address, payments, languages
fluid countries plan DE --mode otg             # preview, changes nothing
fluid countries open DE --mode otg --yes       # add the country, seeded from the atlas
fluid countries prices DE                      # preview converting US prices into EUR
fluid countries prices DE --rate 0.92 --write --yes
fluid countries languages DE                   # which market languages are off, and the command to turn them on
fluid translations enable de --yes
fluid countries agreements DE --create --yes   # the atlas agreements, in every atlas language
fluid countries forms DE                       # the atlas enrollment fields against the country's forms
fluid countries forms DE --create --yes        # the country's enrollment form, as a draft to review
fluid countries status DE                      # check against the atlas

# Translate
fluid translations missing de                  # what isn't translated yet, per type
fluid translations auto de --limit 10          # machine-translate 10 per type, print only
fluid translations auto de --limit 25 --write --yes
fluid translations set products 60311 --lang de --yes --set title="Rote-Bete-Mischung"

Every command prints JSON. Failures print a JSON error on stderr and exit non-zero. Commands that change live configuration, prices or content ask for confirmation unless you pass --yes.

Walks

Both groups have a walk that asks questions in a terminal instead of taking flags. Type < to go back, > to skip, ? for the menu, and Ctrl-C to stop. Each walk saves through the same calls as the commands, and scripts and agents use the commands instead.

• fluid countries walk [iso] opens a country the way Mist does. It asks for the country (searchable) and shows its atlas, then asks the operating mode (each explained in one line), the warehouse, which market languages to turn on, which atlas agreements to create or translate, and whether to keep or change each atlas default: currency, tax, 3-D Secure, payment order and address layout. Then it asks whether to add Fluid's generic defaults and shows a summary to confirm. Nothing is saved before you confirm. It then opens the country, turns on the languages, and creates the agreements. Next it offers the price conversion: it shows the numbers and a sample at the rate you give and saves only on a yes. Finally it hands each market language to the translations walk.
• fluid translations walk [iso] asks for the language if you don't name one, offering to turn it on. It shows what's missing per type, then lets you machine-translate each type in batches. You go through the proposals one at a time to accept, edit or skip, and each one is saved as you accept it. It covers every type, including theme strings and theme page strings.

fluid countries

open takes --warehouse-id, --business-id, --entity-registered and --settlement-currency for what the atlas can't know, and --set key=value to override a seeded value. It skips Fluid's generic country agreements and forms (pass --legacy-defaults to keep them), and changes nothing on an open country unless you pass --reseed, which writes every atlas value over it. To change a few fields on an open country, use update.

Converting prices

fluid countries prices DE reads every active product (--status for others) and, for each variant, multiplies its US price by the rate and rounds it half up to the currency's minor unit (whole units for JPY, KRW and the other zero-decimal currencies, cents for the rest). It prints the rate, the rounding, counts, and a sample of before and after prices. Nothing is saved.

• Rate. Pass --rate: units of the new currency per unit of the source currency. Without it, the preview uses the European Central Bank's daily reference rate. --write always needs --rate, so the rate saved is the one you reviewed.
• Fields. price, subscription_price and compare_price by default. Add wholesale and wholesale_subscription_price with --fields. A field with no source amount is left alone.
• Never free. A variant whose converted price rounds to zero is skipped (roundsToZero), and any other field that rounds to zero is left out.
• Reruns are safe. A variant that already has a price in the country is skipped (alreadyPriced), so a second run never converts a converted price. A price saved in another currency is skipped too (pricedInOtherCurrency). --overwrite replaces both.
• On sale. Converted prices keep the variant's current on-sale state in the country. --activate puts each converted variant on sale.
• Failures. Each variant is saved on its own. A refused save is listed under failed with the API's message, and the rest carry on.
• Changes during the run. Each product is read again just before its variants are saved. A variant that someone priced in the country since the preview is left alone and listed under changedSincePreview.
• Price editor. When the price editor manages the company's prices, priceEditor is true. Each save then goes into the price editor's price lists; one it can't place is listed with refusedByPriceEditor: true. --overwrite is refused for these companies, so a price someone set in the price editor is never replaced from here.

Setting up the enrollment form

Enrollment checkout shows every active Post Purchase form for the cart's country after payment, merged into one. fluid countries forms DE reads those forms and prints, for each atlas enrollment field, the element it maps to and whether enrollment asks for it (collected, inDraft, missing or byHand), with plan: what --create would send. Nothing is saved.

• The form. --create makes Enrollment - <Country>, a Post Purchase form scoped to the country alone, the same form the admin's country checklist makes. If it exists, as a draft or published, the missing fields are added to it instead. --form <id> adds to another Post Purchase form scoped to the country alone.
• Draft first. A new form is a draft, so a person reviews it in the form builder before enrollment asks for it. --activate publishes it (or the existing draft) in the same run.
• Only what's missing. A field any active Post Purchase form for the country already collects is not added again. An identity field (name, email, phone, date of birth) matches by type; any other field by type and label.
• Nothing removed. Adding to a form reads it again and sends back each of its components with its element id, so nothing on it is deactivated and no field's sensitivity changes.
• Other countries. A form shared with other countries is read, never changed: a field one country's atlas asks for doesn't belong on another country's enrollment. What it lacks goes on the country's own form.
• Member types. A Post Purchase form reaches everyone who enrolls in the country, so a field the atlas asks only some member types for (dates of birth, and most tax questions) is listed under byHand with the reason instead. So are multiple choices the atlas gives no choices for.
• Data forms must not collect. An SSN, and any field that takes a value (anything but a yes/no or checkbox) whose label names a national or tax ID number, bank or card details, or a password (a CPF, a TIN, an IBAN), is never created; it's listed under byHand. Collect those through your tax or payout provider.
• Sensitive fields. A date of birth is stored sensitive, so roles without the forms view-sensitive permission see its answers masked. Creating one needs the forms manage-sensitive permission; without it the API refuses the whole save and the command says so. --skip-sensitive creates the rest and lists the ones it left out.

fluid markets ordering and currencies

Every API refusal prints its code and details. Needs the market-config release.

fluid translations

Notes:

• auto translates storefront rows, menu items, agreements and labels from the store's default language, read from the storefront rows (--store-language only when it can't be read). Theme strings translate from the --from locale, en by default. An item the translator returns only part of is listed under incomplete and not saved; --skip <type>:<id> leaves it out of later runs. Items the API refuses are listed under failed. Both count toward remaining.
• A storefront row with any translation counts as translated, because reads fall back to the default for fields without one.
• A label whose translation is the same word as the default (a brand name) stays listed; skip it with --skip labels:<id>.
• missing lists theme keys whose value is still word for word the source under sameAsSource, to review by eye.
• Theme writes publish immediately. A locale file write sends the theme version it read, so a concurrent edit makes it fail instead of overwriting; auto lists every key of a refused write under failed. A theme whose files can't be listed (an invalid member configuration) can be read but not saved, because the write couldn't be guarded. A theme-sections write reads the template again just before saving and merges into it.

Not covered

These have no API that translates them, so they stay in fluid-admin or with a person:

• Promotions (title, description, terms).
• Translations of enrollment form fields and other form labels.
• Fluid's own labels ("New", "Trending"), which Fluid translates.
• Section settings written as literal text rather than as a locale key. Use the page editor's translate mode, which turns the setting into a key, then fluid translations covers it.
• Payment provider onboarding and the launch checklist for a country.

The walkthroughs are the "Open a country" and "Add a language" guided setups at https://docs.fluid.app/setup.