Company reference / Inquiry only

Companycatalogue.

Turn supplied company information into business directory records with traceable sources. Yondexy is a small digital studio in Austin, Texas. Our company catalogue service starts with the entry fields, not a promise of publication. Send a company listing inquiry to discuss the scope.

Pricing basis: company entries, record fields and update instructions, for one record or a defined batch. Service pricing requires an inquiry. No purchasable listings, checkout or payment on this site.

An illustrative company reference entry with an inquiry control
Reference entry / IllustrationNot a client listing or a review of a company.

01 / Catalogue inquiry type

Company catalogue record

An entry is made of attributable facts, not promotional filler.

The company catalogue record is an inquiry-led digital service. It brings a defined set of company fields into a readable reference entry, with a source note and a way to explain later changes. It suits a team preparing a company reference project, or a record owner who needs to describe a proposed entry or correction.

The material is the information you are entitled to supply. A company name and a public contact route may be useful fields; an unsupported badge is not. We define the purpose of a field before presenting it as a fact about the business. The field outline on this page makes that approach inspectable without inventing example companies.

Item
Company catalogue record. A reference entry service, not a listing available for instant purchase.
Input
Authorized company information with source references, plus the intended use of the entry.
Entry structure
Identity and descriptive fields, appropriate public contact information, source notes and an update route.
Record boundary
One company entry or an agreed batch. Associated places can be separate records rather than repeated company profiles.
Price basis
The number of entries and fields, together with update instructions. No published rate or implied cost per listing.
Publication boundary
Sending an inquiry does not publish an entry, create an endorsement or reserve a position in a directory.

Read the structure, not a sales badge.

A useful record lets someone distinguish the company from a similarly named business and understand where a field came from. That is the standard the intake outline serves. It does not assign a quality score or claim that a source has been independently certified.

02 / Entry fields

A public field needs a public purpose.

Start with the smallest entry that performs its intended job. A catalogue built to identify companies needs different detail from one that helps a reader understand a service scope. Copying every column from an internal spreadsheet adds risk without necessarily improving the reference.

Separate a public company contact from the person discussing the project. The email address used to send an inquiry is not automatically a field for publication. That distinction must survive the handoff from intake to entry design.

Company entry field outline, not a live company record
FieldPurpose and boundary
Company identityThe source-supported name and a stable record key. Do not treat a marketing label as a legal name unless the source establishes that relationship.
DescriptionPlain information about what the company does. Keep the description attributable and remove claims the supplied source cannot support.
CategoryA defined classification that helps a reader find the record. A category is not a credential or a statement that the company meets an industry standard.
Public contactA contact route intended for publication. Keep it separate from private project correspondence and do not infer it from another company's pattern.
Location relationshipAn explicitly supported association to a place record. A written address does not by itself establish opening hours or access for visitors.
Source referenceThe origin of the information, with restrictions carried into the scope. Not every internal source reference needs to be displayed publicly.
Update contextWhat was checked or changed, if known. An import date is not a claim that every field was reverified on that date.
Inquiry routeThe route for asking about the entry or requesting a correction. It is not a checkout or an automatic publication instruction.

Keep absent information absent.

A missing contact field should not be filled with a guessed phone number. An unknown operating history should not be written as an established business story. If a fact cannot be supported, omit it or describe the uncertainty where the record's purpose requires that distinction.

This is particularly important in batches. A template can make incomplete records look complete simply by repeating generic language. The intake should identify which fields are consistently available and which need a decision for each entry.

03 / From inquiry to entry scope

Agree what the entry is allowed to say.

A company listing inquiry is the start of review, not a request for automatic publication. The process separates who supplies the information from what can appear in a public reference record. Timing and deliverables are discussed against the actual scope.

  1. Identify the requested record or batch

    At first contact, say whether you need a new entry structure, a batch of business directory records or a correction to an existing entry. Describe your relationship to the supplied information without sending sensitive identity documents.

  2. Establish the source boundary

    Before publication work is agreed, identify where the fields come from and what permission supports their use. Distinguish public company information from private notes supplied only to explain the project.

  3. Set the field and update scope

    Agree the entry unit, the fields that belong in it and how a change is requested. Define whether associated places are separate records. These decisions establish the basis for service pricing.

  4. Review the proposed entry treatment

    Resolve unsupported claims and unclear relationships before implementation. A proposed catalogue entry remains a reference record; it does not become a review or endorsement because the wording has been edited.

The studio approach explains why source and scope lead the work. If the record also needs result filters, that belongs in the website search service rather than being assumed as part of an entry.

04 / Catalogue intake outline

Send the facts and the publication boundary.

You do not need a finished company profile to make an inquiry.

Describe the entry you want to define and the information available to support it. Where the source is incomplete, say which fields are missing. The aim of intake is to make those decisions visible, not to polish uncertain information into a more persuasive claim.

A company entry field checklist being reviewed on a tablet
Illustrative field reviewAn intake checklist, not evidence of a published client entry.

Entry intake outline

For the initial inquiry

Request type. State whether this concerns a new entry, an entry structure for a batch, or a correction. If there is an existing record, identify it without copying unnecessary personal information.

Source ownership. Explain what information you control and which fields come from another source. Note any restrictions on public use.

Field inventory. List the company fields you can supply. Keep public business contact fields apart from the contact details we should use to discuss the project.

Record count. State whether the count means companies, locations or raw source rows. If it is an estimate, label it as one.

Update instruction. Identify how later changes should be requested and what source would support a correction. Do not promise a refresh schedule that the source cannot sustain.

One company is not always one location.

Repeated location rows can inflate a company count. Before treating them as separate entries, decide whether they represent distinct companies or place relationships attached to one company. The right distinction depends on the source and the intended catalogue, not on whichever layout looks fuller.

The place data model keeps location identity separate from company identity. For a source set that must feed an index, the index design worksheet defines the stable keys and update rules. Those decisions prevent a changed address from accidentally creating a second company record.

An entry and a review answer different questions.

A reference entry answers what information is recorded about a company and where that information came from. A review expresses an assessment or describes an experience. Combining the two without a clear distinction gives neutral fields an authority they have not earned.

Yondexy's company catalogue service does not turn a supplied description into an endorsement. The entry does not receive stars, a customer count or an invented verification badge. A category field explains how the record is organized; it does not certify the company.

An inquiry control is also not evidence of a commercial relationship with the company described. Its purpose must be clear: asking about a record or a service scope is different from booking that company's work. The catalogue is inquiry-only, and no entry creates a purchase on this site.

A company listing is a reference record, not a review score.

Yondexy / Catalogue principle

05 / Provenance and correction

A changed field needs a reason you can trace.

Record provenance explains where a field came from. Update instructions explain what should happen when it changes. They belong together, but they are not the same thing. A source link alone does not establish who can request a replacement value.

For a correction, identify the affected entry and the specific field. Describe the proposed change and the source supporting it. A company rename differs from a correction to a spelling error; either may require preserving enough context to avoid confusing it with another business.

Field-level changes

Update only what the source supports. A corrected public email should not silently alter the company description or reset every freshness note. Where a field is withdrawn, the record needs a stated outcome rather than an improvised replacement.

Record-level changes

A merger, closure claim or disputed identity cannot be resolved by changing a label alone. Describe the evidence and the relationship between old and proposed records. Unresolved information may need to remain unpublished while the decision is made.

Update instructions to include in the catalogue scope
QuestionInstruction needed
Which source governs?Identify the authoritative source for the changed field; different fields may have different sources.
What is the evidence?Describe the support for the replacement value without requiring private correspondence to become public.
What remains visible?Decide how a missing or disputed value affects the entry. Avoid presenting a known stale field as current.
Does identity change?Distinguish an edit to the same company record from a new entity or a changed relationship.
How is the change requested?Use the agreed inquiry route and retain the record reference so the request can be connected to the correct entry.

A request involving your own personal data belongs on the data request page. For a business record correction, use the service inquiry route and keep the message focused on the field at issue. Neither route asks for passwords.

A batch still needs individual exceptions.

Shared field rules can make a batch consistent, but a missing source value is still missing for that entry. Include known exceptions in the scope rather than assume every record can use the same description or update instruction.

Send a service inquiry

Catalogue questions

Know what an inquiry starts.

This service is for reference information that can be supported by a source. It is not for buying recommendations or filling a directory with invented business profiles.

Can I buy a company listing on this page?

No. The catalogue is inquiry-only. There is no cart, checkout or online payment. An inquiry is reviewed before any scope or service pricing is agreed, and submission does not guarantee publication. The service and website terms describe that boundary.

Does an entry mean Yondexy recommends the company?

No. A company reference record describes source-supported information. It is not a review score, endorsement, certification or guarantee of a company's work. A record should not be treated as a substitute for the checks relevant to your own decision.

Can an entry contain only the fields we can support?

Yes. The required fields depend on the agreed purpose of the record. Unknown information should remain unknown or be left out, rather than filled with an inferred address, contact or business claim. Where the missing field prevents the entry from doing its job, resolve that gap before publication work is agreed.

What should I send to correct a record?

Identify the entry and field, describe the correction and provide the source that supports it. Do not send passwords or sensitive identity documents in an initial inquiry. Additional context may be needed before a change can be made. No automatic correction deadline is promised on this page.

Company listing inquiry

Ask about one record or a defined batch.

Tell us which company reference fields you have and what the catalogue needs to help a reader understand. If you are working from a batch, distinguish company entries from repeated source rows. If it is a correction, identify the entry before describing the replacement information.

The price basis is the entry count, field scope and update instructions. No amount is implied by a record count alone, and no payment is taken here. Your inquiry gives Yondexy the information needed to discuss the work rather than pretending a generic listing package fits it.

Inquiry-only catalogueSource before entry

Make the record boundary clear.

Use the contact form for the proposed entry or catalogue project. Keep private data out of the initial description. The reply route you supply is used to discuss the inquiry, not assumed to be a public company contact.

Send a service inquiry